-
Bug
-
Resolution: Unresolved
-
Major
-
None
It appears that there's a race condition if a build is queued and configuration changes around the same time.
On http://hudson.drizzle.org/job/drizzle-build/ it appears that if the matrix project only has one axis and is tied to the master, the configuration build doesn't start despite the master node having available executor.
The configuration build remains in the queue with "waiting for available executor", and the link from the queue points to non-existent http://hudson.drizzle.org/job/drizzle-build/default/ where it should point to http://hudson.drizzle.org/job/drizzle-build/label=master/
[JENKINS-5700] Race condition in Matrix project builds between config changes and builds
| Description |
Original:
On http://hudson.drizzle.org/job/drizzle-build/ it appears that if the matrix project only has one axis and is tied to the master, the configuration build doesn't start despite the master node having available executor. The configuration build remains in the queue with "waiting for available executor", and the link from the queue points to non-existent http://hudson.drizzle.org/job/drizzle-build/default/ where it should point to http://hudson.drizzle.org/job/drizzle-build/label=master/ |
New:
It appears that there's a race condition if a build is queued and configuration changes around the same time. On http://hudson.drizzle.org/job/drizzle-build/ it appears that if the matrix project only has one axis and is tied to the master, the configuration build doesn't start despite the master node having available executor. The configuration build remains in the queue with "waiting for available executor", and the link from the queue points to non-existent http://hudson.drizzle.org/job/drizzle-build/default/ where it should point to http://hudson.drizzle.org/job/drizzle-build/label=master/ |
| Summary | Original: Matrix project configuration build doesn't start | New: Race condition in Matrix project builds between config changes and builds |
Monty Taylor
added a comment - I just renamed the drizzle-build job to drizzle-build-matrix, in case it needs to still be looked at.
Monty Taylor
added a comment - I just renamed the drizzle-build job to drizzle-build-matrix, in case it needs to still be looked at. 
Jenkins IRC Bot
made changes -
| Component/s | New: matrix-project [ 18765 ] | |
| Component/s | Original: matrix [ 15501 ] |
| Workflow | Original: JNJira [ 135792 ] | New: JNJira + In-Review [ 174385 ] |
On further investigation it seems like some kind of race condition. If the configuration build is in the queue when the configuration changes, the system gets into an inconsistent state.