I've made a fix for this, just waiting to be merged : https://github.com/jenkinsci/jenkins/pull/419
Vincent 2012/3/28 Daniel Tkatch <[email protected]> > here is a JIRA that looks connected: > https://issues.jenkins-ci.org/browse/JENKINS-12994 > > On Mar 27, 3:29 pm, Paul Weiss <[email protected]> wrote: > > After upgrading I have several jobs in queues that are just not > dequeuing. > > If they are tied jobs the tooltip says "Waiting for next executor on > > <tie-expression>". If they are untied jobs the tooltip says "Waiting for > > next executor". > > > > I have executors available, both for the tied and untied jobs, but they > are > > not being scheduled. I've tried disconnecting and reconnecting the > slaves, > > and adding and removing the executor count. Nothing works. > > > > Sometimes if I delete an unrelated slave, everything will wake up and the > > jobs get scheduled. But right now, my farm is very inefficient. > > > > The only relevant changse that I can see in the logs, that touches > queues, > > are these: > > > > Fixed a bug in executor/queue filtering for matrix projects. (pull > > 394<https://github.com/jenkinsci/jenkins/pull/394> > > ) > > > > Fixed bug where a queued build could start while the previous build was > > still in its post production state. >
