Hi, We upgraded yesterday from 1.424.2 to 1.447.2 and the first problems has started to arrive that we had missed during testing.
We use the parameterized trigger quite heavily, and the issue is that sometimes, about every eight build or so, the upstream build that is waiting for the downstream build that it triggered still waits even though the downstream build has finished long ago. A thread dump reveals that the executor is still waiting in AsyncFutureImpl.get so my guess is that for some reason the thread hasn't been notified about the build result as it should. We also have an in-house plugin doing similar stuff and it can also hang the same way. I haven't found anything that recreates the circumstances yet just the "sometimes it happens" thing on a couple of critical jobs. I've been going through the parts of core I can find that is involved in this; a git diff between Jenkins-1.424.2 and Jenkins-1.447.2 shows some changes in hudson.model.Executor that from what I can see shouldn't affect this, nothing in WorkUnitContext, and maybe something in hudson.model.Queue (but I tend to get lost in there every time I try to understand that code :) ). Does anyone have any hints on where I can continue my investigation or ways of attack to try and recreate the issue to better debug it? Robert Sandell Software Tools Engineer Tools and Integration Sony Mobile Communications Tel: +46 (0)10 80 12721 sonymobile.com<http://sonymobile.com/> [cid:[email protected]]
<<inline: image001.jpg>>
