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

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

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • junit-plugin
    • None
    • Jenkins Version 2.249.3

    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

          timja Tim Jacomb added a comment -

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

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

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

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

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

          timja Tim Jacomb added a comment - It won’t be causing an issue but I’ll take a look to get this sorted
          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.

          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.
          timja Tim Jacomb added a comment -

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

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

          People

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

            Dates

              Created:
              Updated: