-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
Hudson ver. 1.380
I'm using build timeout plugin and there's evident that the build time includes the time a job spent waiting in the build queue.
Let say I have build timeout set to 6 hours. But my job was actually executed for 1 hour or so before the build timeout plugin kicked in and killed it. So that 5 hour difference was actually spent in the build queue waiting for a available slave.
I think it makes more sense to assume build time start ticking only when the job executes
Thanks for looking into it. We observed it happened on a remote slave. I'm trying to reproduce it but could get it to happen at will.
Do you know what happens if the slave and master couldn't communicate? Would a network glitch between the two let to this problem? I'm just trying possible causes so I can reproduce the issue