Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-64344

MissingFieldException: No field 'checksName' found in class 'hudson.tasks.junit.TestResultAction'

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: junit-plugin
    • Labels:
      None
    • Environment:
      Jenkins Version 2.249.3
    • Similar Issues:

      Description

      When upgrading to version 1.44 of the Junit plugin, I start getting the following Jenkins errors for most of my pipelines:

      Downgrading to version 1.43 of the plugin resolves the issue.

       

      If it matters, I'm using Nunit to run our tests and using the attached xslt to convert to the Junit format.  I don't think that's the issue, since it is giving the MissingFieldException for pipelines that don't run any tests as well.

        Attachments

          Activity

          Hide
          timja Tim Jacomb added a comment -

          you can discard the unreadable data, it shouldn't cause any issues

          Show
          timja Tim Jacomb added a comment - you can discard the unreadable data, it shouldn't cause any issues
          Hide
          cdpage Chris Page added a comment -

          The list grows with each pipeline that runs.  Even after discarding, it comes back.  In the text above, it says that it impacts Jenkins startup time, and it shows as an alert for users with the permissions to see alerts.  Whatever is checking for that field needs to fail gracefully such that it does not raise these kind of errors.

          Show
          cdpage Chris Page added a comment - The list grows with each pipeline that runs.  Even after discarding, it comes back.  In the text above, it says that it impacts Jenkins startup time, and it shows as an alert for users with the permissions to see alerts.  Whatever is checking for that field needs to fail gracefully such that it does not raise these kind of errors.
          Hide
          timja Tim Jacomb added a comment -

          It won’t be causing an issue but I’ll take a look to get this sorted

          Show
          timja Tim Jacomb added a comment - It won’t be causing an issue but I’ll take a look to get this sorted
          Hide
          jonesbusy Valentin Delaye added a comment -

          Same issue here after upgrading form junit:1.43 to junit:1.46 and core 2.263.1

          Show
          jonesbusy Valentin Delaye added a comment - Same issue here after upgrading form junit:1.43 to junit:1.46 and core 2.263.1
          Hide
          timja Tim Jacomb added a comment -

          this should be fixed if you configure your job and save it

          Show
          timja Tim Jacomb added a comment - this should be fixed if you configure your job and save it

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            cdpage Chris Page
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated: