-
Bug
-
Resolution: Fixed
-
Minor
-
None
FutureImpl does not cancel its attribute start, which is AsyncFutureImpl instance for identification that task is running.
methos setAsCancelled() should cancel its attribute start too.
It causes bug in method getStartCondition() in case cancellation of job in queue. Because start AssyncFuturaImpl is not set as cancelled and thread wich called getStartCondition() wait forever when job is cancelled in queue, because start is never cancelled.
It can be seen in Build flow plugin.
Code changed in jenkins
User: Eugene Baranov
Path:
core/src/main/java/hudson/model/queue/FutureImpl.java
test/src/test/java/hudson/model/QueueTest.java
http://jenkins-ci.org/commit/jenkins/3edae667b3955a561296a23122f86b35ec928a98
Log:
JENKINS-25514Fixed lock case in FutureImplwhen some other process is waiting for build in queue.