![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Lucie Votypkova
|
|
Components:
|
core |
|
Created:
|
10/Nov/14 12:14 PM
|
|
Description:
|
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.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Lucie Votypkova
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
