• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • Jenkins on Ubuntu Lucid Lynx with build slave on Windows XP

      Test results are missing on all but the last build, i.e., the build and test result overview page still displays the number of failed tests, but the concrete tests are not listed/linked (see attachment and our build server).

          [JENKINS-15503] Test results lost on all past builds

          Sven Amann added a comment -

          I made a downgrade to 1.484 due to other issues and all missing results are back again, so, no actual data loss is experienced!
          Unfortunately though, the "missing" test results messed up some unstable/stable states.

          Sven Amann added a comment - I made a downgrade to 1.484 due to other issues and all missing results are back again, so, no actual data loss is experienced! Unfortunately though, the "missing" test results messed up some unstable/stable states.

          Chris Cooper added a comment -

          I have this same problem, I'd like to add that the link on the module is set to /jenkins/testReport

          Chris Cooper added a comment - I have this same problem, I'd like to add that the link on the module is set to /jenkins/testReport

          piepera added a comment -

          This issue is affecting us as well, although it arises a little differently. Half of our projects display this broken "Test Results" page for all builds – new builds and old builds. The other half of our projects work fine for all builds – new builds and old builds.

          We haven't been able to figure out the pattern for which projects produce the error, and which don't.

          piepera added a comment - This issue is affecting us as well, although it arises a little differently. Half of our projects display this broken "Test Results" page for all builds – new builds and old builds. The other half of our projects work fine for all builds – new builds and old builds. We haven't been able to figure out the pattern for which projects produce the error, and which don't.

          Sven Amann added a comment - - edited

          For us the bug disappeared with upgrade to 467. Unfortunately now there is JENKINS-15601 (just so you know in case you consider an update)

          Sven Amann added a comment - - edited For us the bug disappeared with upgrade to 467. Unfortunately now there is JENKINS-15601 (just so you know in case you consider an update)

          piepera added a comment -

          Sven, you mean 1.487, not 1.467, correct??

          piepera added a comment - Sven, you mean 1.487, not 1.467, correct??

          Sven Amann added a comment -

          Ups, sure do! Sorry for the typo!

          Sven Amann added a comment - Ups, sure do! Sorry for the typo!

          Sven Amann added a comment -

          The issue has vanished for me as of version 1.487 (stable till 1.489), I consider this as resolved.

          Sven Amann added a comment - The issue has vanished for me as of version 1.487 (stable till 1.489), I consider this as resolved.

          We're still experiencing these issues frequently even on a recent 1.530 version We upgraded from 1.526 which showed the same symptoms as well.

          Patrick Cornelißen added a comment - We're still experiencing these issues frequently even on a recent 1.530 version We upgraded from 1.526 which showed the same symptoms as well.

            Unassigned Unassigned
            salsolatragus Sven Amann
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: