• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Trivial Trivial
    • xunit-plugin
    • None

      The test for old test results is a little short. 4.1 seconds doesn't seem too old to me.

      13:41:34 [xUnit] [ERROR] - Test reports were found but not all of them are new. Did all the tests run?
      13:41:34 * /nfshomes/hudson/.hudson/jobs/grex-bps-geodesy/workspace/bps/geodesy-cpp/build/test/cpptestresults.xml is 4.1 sec old
      13:41:34

          [JENKINS-17520] xUnit check for old tests is too short

          At the moment, the plugin expects that the last modified date of test results were updated at build time (created by the plugin or the touch command is applied for example).
          The plugin tests that the test reports last modified date is inferior to 3 s.
          What is your build time?
          Moreover, you are able to check an option in the configuration to not activate this check.

          Gregory Boissinot added a comment - At the moment, the plugin expects that the last modified date of test results were updated at build time (created by the plugin or the touch command is applied for example). The plugin tests that the test reports last modified date is inferior to 3 s. What is your build time? Moreover, you are able to check an option in the configuration to not activate this check.

          jpschewe added a comment -

          The time at the top of the job is Apr 8, 2013 1:40:36 PM. This particular build took 59 seconds.

          I found the checkbox, that's why I marked this trival for priority. I'm able to work around this by checking the box.

          jpschewe added a comment - The time at the top of the job is Apr 8, 2013 1:40:36 PM. This particular build took 59 seconds. I found the checkbox, that's why I marked this trival for priority. I'm able to work around this by checking the box.

          I did a mistake. 3 seconds is the delay between the start build time and the last modified date of the report file.
          The objective is to not take reports from previous build if you don't have do a clean.

          Is it still a issue for you?

          Gregory Boissinot added a comment - I did a mistake. 3 seconds is the delay between the start build time and the last modified date of the report file. The objective is to not take reports from previous build if you don't have do a clean. Is it still a issue for you?

          jpschewe added a comment -

          If I disable the check,then I'm fine. I always do a clean, so this is fine for me. But you'll probably want to increase the timeout or make it configurable to make it useful. If a system is loaded it could be a few seconds between when cppcheck is run and the plugin is executed.

          jpschewe added a comment - If I disable the check,then I'm fine. I always do a clean, so this is fine for me. But you'll probably want to increase the timeout or make it configurable to make it useful. If a system is loaded it could be a few seconds between when cppcheck is run and the plugin is executed.

          From 1.78, you have a suitable xUnit plugin which enable you to set the delay before failing build.

          Gregory Boissinot added a comment - From 1.78, you have a suitable xUnit plugin which enable you to set the delay before failing build.

            gbois Gregory Boissinot
            jpschewe jpschewe
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: