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

Test failures that are archived while a build is still running don't show up until run is finished

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • blueocean-plugin
    • None
    • Blue Ocean - Candidates

      I am sure cliffmeyers mentioned this to me, but I have noticed. 

       

      if you run a project, say like kzantow/failure-project, and write a long running pipeline that archives test failures early on in the pipeline - they do not show up in blue ocean until run completed. 

       

      In classic they are already visible. 

       

      Testing Notes: 

      • Will require an E2E test that runs a test with archived results in an earlier stage, confirm is shows up

          [JENKINS-47044] Test failures that are archived while a build is still running don't show up until run is finished

          Michael Neale created issue -
          Michael Neale made changes -
          Epic Link New: JENKINS-36296 [ 172305 ]

          Cliff Meyers added a comment - - edited

          michaelneale In your testing, do you know if you opened the Tests tab UI before the tests would have been archived in the pipeline, or after? Or does it make no difference?

          Cliff Meyers added a comment - - edited michaelneale In your testing, do you know if you opened the Tests tab UI before the tests would have been archived in the pipeline, or after? Or does it make no difference?
          James Dumay made changes -
          Sprint Original: Blue Ocean 1.4 - candidates [ 326 ] New: Blue Ocean 1.4 - beta 2 [ 416 ]
          James Dumay made changes -
          Rank New: Ranked higher

          Michael Neale added a comment -

          cliffmeyers after. 

          Michael Neale added a comment - cliffmeyers after. 
          Michael Neale made changes -
          Description Original: I am sure [~cliffmeyers] mentioned this to me, but I have noticed. 

           

          if you run a project, say like kzantow/failure-project, and write a long running pipeline that archives test failures early on in the pipeline - they do not show up in blue ocean until run completed. 

           

          In classic they are already visible. 
          New: I am sure [~cliffmeyers] mentioned this to me, but I have noticed. 

           

          if you run a project, say like kzantow/failure-project, and write a long running pipeline that archives test failures early on in the pipeline - they do not show up in blue ocean until run completed. 

           

          In classic they are already visible. 

           

          Testing Notes: 

          * Will require an E2E test that runs a test with archived results in an earlier stage, confirm is shows up

          Cliff Meyers added a comment -

          michaelneale interesting, so that leads me to believe it's a bug on the server side since the REST endpoint would have been fetched after the tests were archived.

          Cliff Meyers added a comment - michaelneale interesting, so that leads me to believe it's a bug on the server side since the REST endpoint would have been fetched after the tests were archived.
          James Dumay made changes -
          Sprint Original: Blue Ocean 1.4 - beta 3 [ 416 ] New: Blue Ocean 1.4 - beta 4 [ 441 ]

            Unassigned Unassigned
            michaelneale Michael Neale
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: