That history for the last 16 hours is mainly me triggering builds manually. When I submit regression tests manually they're never picked up unless I go kick off-line slaves – they never wake up by themselves.
New changes submitted to gerrit in the last 24 hours have not had any automatic regression runs. Needless to say, this is not a good time for this to happen as we try to get bug fixes through review for rhgs-3.1. ----- Original Message ----- > From: "Niels de Vos" <[email protected]> > To: "Kaleb Keithley" <[email protected]> > Cc: "Gluster Infrastructure" <[email protected]> > Sent: Tuesday, June 23, 2015 3:30:05 AM > Subject: Re: [Gluster-infra] jenkins not running regressions > > On Mon, Jun 22, 2015 at 08:31:49PM -0400, Kaleb Keithley wrote: > > > > I've rebooted many of the slaves, but most of them are still sitting > > idle and about 90% of the changes submitted in the last 12+ hours have > > not had their regression tests run. > > > > Anyone have any ideas? > > I dont know, the queue of regression tests is rather empty. Do you mean > regression tests are not scheduled at all? There is a nice history on > http://build.gluster.org/job/rackspace-regression-2GB-triggered/ that > shows many (failed) test runs. > > Could it be that there is an issue with the reporting back of the test > results to Gerrit? Which patch did not get any test results, maybe I can > figure out why that happened. > > Thanks, > Niels > _______________________________________________ Gluster-infra mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-infra
