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

JUnit Plugin should not follow symlinks when finding test report XML files

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • junit-plugin
    • None

      When the plugin searches for test report XML files, it follows symlinks. This can cause a single XML file to be found more than once (possibly the cause of JENKINS-17822), or infinite recursion (JENKINS-40999).

          [JENKINS-52549] JUnit Plugin should not follow symlinks when finding test report XML files

          Richard Fearn created issue -
          Richard Fearn made changes -
          Link New: This issue relates to JENKINS-40999 [ JENKINS-40999 ]
          Richard Fearn made changes -
          Link New: This issue relates to JENKINS-17822 [ JENKINS-17822 ]

          Richard Fearn added a comment -

          On closer inspection I see that when test results are merged together, TestResult looks at the timestamp of each SuiteResult to determine whether it's a duplicate. So in the case of 'proper' JUnit report XML files, that include a timestamp, duplicate results should be discarded. So following symlinks is unlikely to be the cause of JENKINS-17822 (nowadays, at least).

          We are producing test report XML files (from Python tests run using Jython) that don't include a timestamp, so the 'duplicate' results aren't being discarded.

          Richard Fearn added a comment - On closer inspection I see that when test results are merged together, TestResult looks at the timestamp of each SuiteResult to determine whether it's a duplicate. So in the case of 'proper' JUnit report XML files, that include a timestamp, duplicate results should be discarded. So following symlinks is unlikely to be the cause of JENKINS-17822 (nowadays, at least). We are producing test report XML files (from Python tests run using Jython) that don't include a timestamp, so the 'duplicate' results aren't being discarded.

          Richard Fearn added a comment -

          Our rest report XML files are being written by xmlrunner, which has been updated to include a timestamp. (We don't currently have this fix, but I'll put it in.)

          Richard Fearn added a comment - Our rest report XML files are being written by xmlrunner , which has been updated to include a timestamp. (We don't currently have this fix, but I'll put it in.)

            Unassigned Unassigned
            richardfearn Richard Fearn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: