-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Platform: Sun, OS: SunOS
When there is a Job in the Build Executor that forces two other jobs to block
and wait (all three jobs have the same Lock name), when the job in the executor
finishes both blocking jobs enter the Executor. I believe the desired behavior
would be for one of the two blocking jobs to enter the Executor, and the other
to now block on the newly executing job.
Summary of current behavior:
Job A (w/ Lock "Long Running") is executing
Job B (w/ Lock "Long Running") is blocking in the Build Queue on Job A
Job C (w/ Lock "Long Running") is blocking in the Build Queue on Job A
Job A finishes
Job B AND C enter execution even though one should enter and block the other