At 11:32 05.02.2023, you wrote: >Hello > >I have a pipeline with several steps. Three of those call a function to do the >work, working in parallel. The job itself works fine, everything is executed >as intended. However the display of the stages on the job page has wrong >run times. > >The first of the three stages has correct run time of "44min 43s", and below >in small "(paused for 1ms)". However the other two stages look differently. >Both have a run time of "0ms" and below "(paused for 46min 12s)" and >"(paused for 49min 2s)". Looking at the logs that's about the real run time, >just displayed at the wrong place. > >What could be the reason for this wrong display? I'm using the Lockable >Resource Plugin, sometimes with skipIfLocked: true. Could this throw >off the run time calculation? Is there a way to debug this?
Replying to myself: The lock really seems to be the culprit. If the resource is already locked then the stage doesn't need to wait and can continue with the rest of the code. However Jenkins/the plugin/whoever still thinks that this stage is waiting, therefore the wrong timing. I replaced the lock with some other code and now the run times are shown correctly. bye Fabi -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9199960b2bb456622093748874588b31%40indel.ch.