On Tue, Nov 3, 2015 at 9:48 PM, Michael Scherer <msche...@redhat.com> wrote: > Le dimanche 01 novembre 2015 à 12:12 +0530, Kaushal M a écrit : >> On Sun, Nov 1, 2015 at 11:37 AM, Kaushal M <kshlms...@gmail.com> wrote: >> > The mentioned jobs aren't being run, because the slave's running the 2 >> > jobs are offline. This has lead to the build of a huge build queue in >> > jenkins. I'll be disabling them till we get the slave's back online. >> > >> > ~kaushal >> >> I've enabled freebsd-smoke after restarting the slave. >> >> The ci.gluster.org fedora slave is not reachable. Possibly the vpn >> connection has been lost. > > It was not voting afaik, until we fixed the build, so it shouldn't be a > big issue.
Helping you fix this has been on my AI list for several weeks now. I'd like to launch these jobs manually to check out the failures. But Jenkins isn't able to resolve the fedora-22-1 slave. I'm able to ping the slave from the host though. Maybe jenkins needs to be restarted. > > -- > Michael Scherer > Sysadmin, Community Infrastructure and Platform, OSAS > > > > _______________________________________________ > Gluster-infra mailing list > Gluster-infra@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-infra _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
