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

During pipeline step duration reported incorrectly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • blueocean-plugin
    • jenkins version 2.49
      Blue Ocean version 1.0.0-b25
      Java version 1.8
    • 1.0, Blue Ocean 1.0-rc3, Blue Ocean - 1.1-beta-1

      I noticed that during a pipeline stage the build time was reporting an impossible time.  After the stage finished, the time corrected itself.  Screenshots attached.  

        1. Capture.PNG
          Capture.PNG
          5 kB
        2. Capture2.PNG
          Capture2.PNG
          7 kB
        3. Mar-13-2017 14-00-57.gif
          Mar-13-2017 14-00-57.gif
          84 kB
        4. localhost.har
          1.07 MB
        5. 12.xml
          0.7 kB
        6. jenkins-42636-build-dirs.zip
          78 kB

          [JENKINS-42636] During pipeline step duration reported incorrectly

          Stephen Catt created issue -
          James Dumay made changes -
          Sprint New: 1.0 [ 221 ]
          James Dumay made changes -
          Rank New: Ranked lower
          James Dumay made changes -
          Epic Link New: JENKINS-35750 [ 171713 ]
          James Dumay made changes -
          Assignee New: Vivek Pandey [ vivek ]

          James Dumay added a comment -

          Vivek and I suspect this is a backend issue. I've seen this live on blueocean.io

          James Dumay added a comment - Vivek and I suspect this is a backend issue. I've seen this live on blueocean.io
          James Dumay made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]

          Vivek Pandey added a comment - - edited

          jamesdumay I tried fetching 'General SCM' step using step API, its returning correct duration, while General SCM step is going on, it shows that steps duration as running/unknown, and it fetch of that API shows correct incrementing duration. Once its finished/success this number doesn't change. Someone from UI should take a look to see if there is some logic and for some reason its failing to update the duration, because it doesn't happen in all cases.

          It will also help to capture steps API output when it shows such ever increasing duration. I don't see this behavior in API.

          Vivek Pandey added a comment - - edited jamesdumay I tried fetching 'General SCM' step using step API, its returning correct duration, while General SCM step is going on, it shows that steps duration as running/unknown, and it fetch of that API shows correct incrementing duration. Once its finished/success this number doesn't change. Someone from UI should take a look to see if there is some logic and for some reason its failing to update the duration, because it doesn't happen in all cases. It will also help to capture steps API output when it shows such ever increasing duration. I don't see this behavior in API.
          James Dumay made changes -
          Attachment New: Mar-13-2017 14-00-57.gif [ 36412 ]

          James Dumay added a comment - - edited

          vivek can you please check again? I used https://github.com/i386/app-store-demo and was able to reproduce it on almost every second run. I would like to know for certain that this isn't a backend issue.

          svanoort do you know of any conditions where steps could have really huge durations?

          James Dumay added a comment - - edited vivek can you please check again? I used https://github.com/i386/app-store-demo and was able to reproduce it on almost every second run. I would like to know for certain that this isn't a backend issue. svanoort do you know of any conditions where steps could have really huge durations?

            abayer Andrew Bayer
            scatt Stephen Catt
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: