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

Age column could take into consideration aborted run

    • Icon: Improvement Improvement
    • Resolution: Incomplete
    • Icon: Minor Minor
    • xunit-plugin
    • None
    • Jenkins 2.346.1
      xUnit plugin Version3.1.0
      xUnit Categories Extension plugin Version1.1

      Considering an run that is facing an issue (run over the timeout threshold for example), we are facing the below issue for the unit test foo : 

      • Run 0 : Test foo Passed
      • Run 1 : Test foo failing, Age 1
      • Run 2 : Test foo failing, age 2
      • Run 3 : Test foo failing, age 3
      • Run 4 : Run over the threshold (10mins), unit test foo has not beed played, 
      • Run 5 : Test foo failing, age 1
      • Run 6 : test foo failing age 2

      We wrongly believe that the run 5 is responsible for making the unit test failing.

      I believe we should display on run 6 an age of 6.

      This would requiere a paradigm shift from : Age is the run where status = Failed and Previous Run != Failed to 
      Age is the run where status = Failed and Previous run = Passed. 
      Or When a run is aborted and a status is different then Pass, we go through the previous run 

          [JENKINS-69428] Age column could take into consideration aborted run

          florian gouze created issue -
          florian gouze made changes -
          Description Original: Considering an run that is facing an issue (run over the timeout threshold for example), we are facing the below issue for the unit test foo : 
           * Run 0 : Test foo Passed
           * Run 1 : Test foo failing, Age 1
           * Run 2 : Test foo failing, age 2
           * Run 3 : Test foo failing, age 3
           * Run 4 : Run over the threshold (10mins), unit test foo has not beed played, 
           * Run 5 : Test foo failing, age 1
           * Run 6 : test foo failing age 2

          We wrongly believe that the run 5 is responsible for making the unit test failing.

          I believe we should display on run 6 an age of 6.

          This would requiere a paradigm shift from : Age is the run where status = Failed and Previous Run != Failed to 
          Age is the run where status = Failed and Previous run = Passed
          New: Considering an run that is facing an issue (run over the timeout threshold for example), we are facing the below issue for the unit test foo : 
           * Run 0 : Test foo Passed
           * Run 1 : Test foo failing, Age 1
           * Run 2 : Test foo failing, age 2
           * Run 3 : Test foo failing, age 3
           * Run 4 : Run over the threshold (10mins), unit test foo has not beed played, 
           * Run 5 : Test foo failing, age 1
           * Run 6 : test foo failing age 2

          We wrongly believe that the run 5 is responsible for making the unit test failing.

          I believe we should display on run 6 an age of 6.

          This would requiere a paradigm shift from : Age is the run where status = Failed and Previous Run != Failed to 
          Age is the run where status = Failed and Previous run = Passed. 
          Or When a run is aborted and a status is different then Pass, we go through the previous run 
          florian gouze made changes -
          Component/s New: xunit-plugin [ 15636 ]
          Component/s Original: nunit-plugin [ 15562 ]
          Environment Original: Jenkins 2.346.1
          NUnit plugin Version0.27
          xUnit plugin Version3.1.0
          xUnit Categories Extension plugin Version1.0-SNAPSHOT (private-08/16/2018 11:14-atamaill082807)
          New: Jenkins 2.346.1
          xUnit plugin Version3.1.0
          xUnit Categories Extension plugin Version1.1
          Shin-ichi Morita made changes -
          Assignee Original: Shin-ichi Morita [ smorita ] New: Nikolas Falco [ nfalco ]
          Nikolas Falco made changes -
          Resolution New: Incomplete [ 4 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            nfalco Nikolas Falco
            fgouze080321 florian gouze
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: