The erroneous 1 is caused by a change in 2013. https://github.com/jenkinsci/jenkins/pull/742
Now to track down the 0. - Thomas On 2/9/15, 9:44 AM, "Suckow, Thomas J" <[email protected]> wrote: >Looking into this further I come across this interesting nugget: > >println( >Jenkins.getInstance().unlabeledNodeProvisioner.stat.computeQueueLength() ) >println( Label.get("my&&label").nodeProvisioner.stat.computeQueueLength() >) > >Gives: >1 >0 > >Meaning, it is on a queue as unlabeled. Yet, the only job in the queue >states: "pending‹All nodes of label Œmy&&label¹ are offline" > > >Anyone have ideas about how this might occur? > >- >Thomas > > > > >From: <Suckow>, Thomas Suckow >Subject: Re: Cloud slave never provisioned (sometimes) > > >I am not convinced that the durable task plugin is to blame. > >I am seeing a long line of: >FINE hudson.slaves.NodeProvisioner >Queue length 0 is less than the idle capacity 0. No provisioning strategy >required > >Yet I have 8 jobs in the build queue. Something is afoot. I'l keep digging >when I have > time. Any input on where I should look next is appreciated. > > >From: Stephen Connolly >Subject: Re: Cloud slave never provisioned (sometimes) > > >Note there was another deadlock found. There is an open pull request >pending to fix that one > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/D0FE7F00.ED60%25thomas.suckow%40pnnl.gov. For more options, visit https://groups.google.com/d/optout.
