[Gluster-infra] jenkins not running regressions
Niels de Vos
ndevos at redhat.com
Tue Jun 23 10:46:44 UTC 2015
On Tue, Jun 23, 2015 at 05:49:57AM -0400, Kaleb Keithley wrote:
> 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
> New changes submitted to gerrit in the last 24 hours have not had any
> automatic regression runs.
It seems the connection between Jenkins and Gerrit broke. If the ball on
http://build.gluster.org/gerrit-trigger/ is "red", you can click it to
re-connect Jenkins to Gerrit. If that works, the ball turns "blue".
(Re)triggering tests can be done through this form:
> 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" <ndevos at redhat.com>
> > To: "Kaleb Keithley" <kkeithle at redhat.com>
> > Cc: "Gluster Infrastructure" <gluster-infra at gluster.org>
> > 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
More information about the Gluster-infra