On 11 Mar 2015, at 08:45, Emmanuel Dreyfus <manu@xxxxxxxxxx> wrote: > Hi > > Jenkins recently changed behavior: the hosts are now disabled by default > and jobs are queued. I have to explicitely start the hosts in Jenkins > to get regression running. My suspicion is that the Jenkins master is too starved for CPU. All 6 CPU's in it are running 100% constantly, and seem to have been for weeks. No idea why it's changed this behaviour though. :( > Any idea of what goes wrong? > > And by the way I think we have a window to enable voting now. I'm working on stuff for a new Jenkins setup atm (experimenting with VM's and stuff locally ay my house), and this is one of the things on my list to solve. :) + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
