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

Make checking for modification time of junit results be configurable and off by default

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Blocker
    • Resolution: Unresolved
    • Component/s: junit-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      The JUnit Result Archiver will fail the build if the test result files that match the filemask do not have a very recent modification time. The error message it prints is this:
      "Test reports were found but none of them are new. Did tests run?"

      This can be inconvenient in several settings; notably, when the clocks on the master and slave fall out of sync, or when the test results were generated by some process that isn't part of the build itself – maybe they were scp'd from somewhere else, for instance. Or for testing the JUnitResultArchiver itself.

      In my opinion, the behavior should be changed such that check-for-recent-modifications should be off by default. Additionally, the user should be able to specify a "recent" threshold via a setting.

        Attachments

          Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-5393 Jenkins falsely fails builds due to aggressive up-to-date check on junit artifacts

          • Major - Major loss of function.
          • Open
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-18148 JUnit Test Result Report Silently Ignores Files With Old Timestamps?

          • Major - Major loss of function.
          • Resolved
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-9438 Gradle CI builds fail when no test tasks are run

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-47315 No new tests found should be treated as empty results

          • Major - Major loss of function.
          • In Progress
          links to

          Web Link CloudBees Internal OSS-2657

            Activity

            Ascending order - Click to sort in descending order
            16 older comments
            Hide
            Permalink
            sourmonk Justin McMillan added a comment - - edited

            I'm also blocked by this – I use a single Jenkins pipeline job to execute tests (across multiple environments – we want reporting on a per-environment level), and then another job executes which pulls those JUnit results into the workspace, and builds a report. I am encountering this on XMLs that are ~5 seconds "old".

             

            This Powershell script works, but still not the greatest:

            $files = Get-ChildItem "${WORKSPACE}"
  foreach ($i in $files) {
  $i.LastWriteTime = $(Get-Date)
}
            Show
            sourmonk Justin McMillan added a comment - - edited I'm also blocked by this – I use a single Jenkins pipeline job to execute tests (across multiple environments – we want reporting on a per-environment level), and then another job executes which pulls those JUnit results into the workspace, and builds a report. I am encountering this on XMLs that are ~5 seconds "old".   This Powershell script works, but still not the greatest: $files = Get-ChildItem "${WORKSPACE}" foreach ($i in $files) { $i.LastWriteTime = $(Get-Date) }
            Hide
            Permalink
            mkobit Mike Kobit added a comment -

            Echoing what Alex Dubrouski said, this totally breaks incremental builds from tools like Gradle.

            Show
            mkobit Mike Kobit added a comment - Echoing what Alex Dubrouski said, this totally breaks incremental builds from tools like Gradle.
            Hide
            Permalink
            laeubi Christoph Läubrich added a comment -

            Is there any progress on this? We are also hit by this, so currently we have only the option to disable junit recording at all...

            Show
            laeubi Christoph Läubrich added a comment - Is there any progress on this? We are also hit by this, so currently we have only the option to disable junit recording at all...
            Hide
            Permalink
            postman Per Östman added a comment -

            This one is nine (9) years old. Come on, please fix this!

            Show
            postman Per Östman added a comment - This one is nine (9) years old. Come on, please fix this!
            Hide
            Permalink
            zaktaccardi Zak Taccardi added a comment -

            Note: I filed this too on GitHub which is related https://github.com/jenkinsci/junit-plugin/issues/201

            Show
            zaktaccardi Zak Taccardi added a comment - Note: I filed this too on GitHub which is related  https://github.com/jenkinsci/junit-plugin/issues/201

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              bshine bshine
              Votes:
              51 Vote for this issue
              Watchers:
              47 Start watching this issue

                Dates

                Created:
                Updated: