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

Diff stats to previous test build are wrong if previous test build was canceled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Minor Minor
    • tap-plugin
    • None

      If a test build was canceled like at [1] then there obviously are no stats about the number of failed / passed tests available. Currently, this leads to the next build at [2] to display no relative stats but just "TAP Test Results (69 failures )". I would expect the TAP plugin to take only a previously completed test build into account when calculating the relative stats. I.e. the build at [1] should use the build at [3] to calculate the relative stats and "TAP Test Results (69 failures / -60)" in this particular case.

      [1] http://mingwgitdevenv.cloudapp.net/job/mingwGitDevEnv-test/9/
      [2] http://mingwgitdevenv.cloudapp.net/job/mingwGitDevEnv-test/10/
      [3] http://mingwgitdevenv.cloudapp.net/job/mingwGitDevEnv-test/8/

          [JENKINS-19262] Diff stats to previous test build are wrong if previous test build was canceled

          Bruno P. Kinoshita added a comment -

          Hi Sebastian!

          Agreed, +1, let's do as you suggest thanks

          Bruno P. Kinoshita added a comment - Hi Sebastian! Agreed, +1, let's do as you suggest thanks

          Bruno P. Kinoshita added a comment -

          Closing as cannot reproduce.

          Sebastian, I could not reproduce this issue any more. I believe that since it was reported, the Jelly/Java files changed, and the diff was disabled either in Jenkins JUnit plug-in (which we use classes for certain views) or in our own code.

          If you can reproduce, and could include a bit more of information such as Jenkins version, tap plug-in version, and maybe some screen shots, then feel free to bump this issue and I will investigate again.

          Thanks
          Bruno

          Bruno P. Kinoshita added a comment - Closing as cannot reproduce. Sebastian, I could not reproduce this issue any more. I believe that since it was reported, the Jelly/Java files changed, and the diff was disabled either in Jenkins JUnit plug-in (which we use classes for certain views) or in our own code. If you can reproduce, and could include a bit more of information such as Jenkins version, tap plug-in version, and maybe some screen shots, then feel free to bump this issue and I will investigate again. Thanks Bruno

            kinow Bruno P. Kinoshita
            sschuberth Sebastian Schuberth
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: