jamesdumay Does it really make sense to class it as a "major" issue, if it's only rarely reproducible, in one environment, for a brief period?  People will get annoyed about anything, but this doesn't break functionality, only show something bogus for a brief period.

svanoort have seen a few people bring it up - but not in a major way, it happens I would say "often", it smore that people don't often see that screen while it is happening. 

fwiw, I've seen this pop up a few times myself. jamesdumay Do you by any chance have the build directory for one of those runs where this is happening?

abayer I am able to make this happen using the app-store-demo project as mentioned in vivek's comment

It takes a few goes to do it. Seems to happen more frequently if I run Blue Ocean via hpi:run

jamesdumay But you don't have a zip file of a build directory when this is happening, right? =) Just wanna avoid duplicating work if I can!

abayer not on hand sorry

s'alright, s'alright - I'll try to get one myself now.

Ok, I've finally reproduced it. For what it's worth, it's not even the duration of the step, let alone the stage, that the TimingAction is missing - it's <2 seconds total. I was copying the build directory aside every second. One copy, before 12.xml was written (i.e., before the docker pull started), all was fine. Next copy, one second later, 12.xml was there, 12.log was completely empty, and 12.xml didn't have a TimingAction. And one second after that, 12.xml was still the latest, 12.log had some output in it, and 12.xml did have a TimingAction. So the shell step calling docker pull was still running but the node now had a proper TimingAction. While the time-since-epoch duration seems to stick around in the UI after that, that's something in the UI not refreshing it from the API, because a reload of the page gets the right duration at that point.

I'll defer to svanoort if he's got a better sense of what might be happening here, but I'd guess it's just that there's a tiny tiny tiny window between when the FlowNode is created and first saved and when CpsFlowExecution.notifyListeners gets called, which leads to the actual adding of the TimingAction. 

So frankly? I think Blue Ocean should just be a little smarter and either not display a duration at all if it's expecting a TimingAction but gets null, or it should somehow decide what an appropriate analogue for the start time would be. This tiny gap between the FlowNode being initially written and the TimingAction being added is, IMO, entirely reasonable.

fwiw, added jenkins-42636-build-dirs.zip as an attachment. It's got the three separated-by-1-second copies of the build directory I mentioned in the above comment.

PR up at https://github.com/jenkinsci/blueocean-plugin/pull/947 - not sure off the top of my head the right way to test it, since reproducing the issue is inconsistent and timing-based anyway.