Vivek Pandey this looks related https://ci.blueocean.io/blue/organizations/jenkins/blueocean/detail/story%2FJENKINS-38847/3/pipeline/

https://gist.github.com/i386/3817e2b8347f030288c9c41aa6d61895

! blueocean #3 2016-10-28 10-38-29.png|thumbnail!

James Dumay Log doesn't show there was any error in that finally block. However overall run is marked as failed. Something ate that error away. I am going to isolate it as test case and see if I can reproduce. Maybe its underlying library bug.

James Dumay yeah that step is eating away the error. I suspect the finally block is fine as there is no error in the finally block, however I see errors during node compilation. The pipeline code should be printing error before marking the build as failed.

...
 } catch(err) {
        currentBuild.result = "FAILURE"
      } finally {
        sendhipchat()
        deleteDir()
      }

James Dumay Michael Neale https://ci.blueocean.io/blue/organizations/jenkins/blueocean/detail/story%2FJENKINS-38847/3/pipeline/ definitely is not right. There is bug in step's status calculation, where its using:

            GenericStatus status = StatusAndTiming.computeChunkStatus(run, before, atomNode, atomNode, after);

This is wrong. this is resulting in computing step's status as chunk vs as individual FlowNode. Fix is in progress.

ah well spotted. I think this has bit a few people (likely some duplicate tickets too)

Vivek Pandey where can I find the issue tracking the fix for the step calculation bug? Is it JENKINS-38759 ?

James Dumay This was that ticket where I fixed it. Or you mean bug to fix bismuth API to calculate status of individual steps using StatusAndTiming.computeChunkStatus(run, before, atomNode, atomNode, after)? I have not opened one. I guess it might be more like RFE vs fix as this API is intended for chunks and I was hoping it to work for individual step.

Thanks Vivek Pandey