Ah, I see. Thanks for cleaning everything up! On Mon, Apr 29, 2019 at 6:13 AM Laszlo Gaal <laszlo.g...@cloudera.com> wrote:
> > > > It should be possible to configure the pre-review job so at most N jobs > run > > at once. I think the rest will then properly queue up. > > > That's actually what happened -- it was the unusually long build queue that > caught my attention. > It was pretty quick to find what caused the build requests, and to verify > with the submitter > that none of these submissions are worth checking. > Jenkins was suspended to isolate the build requests that had to be killed, > and to prevent > new build requests from being created during the churn of the cleanup > process. > > On Mon, Apr 29, 2019 at 2:30 PM Jim Apple <j...@jbapple.com> wrote: > > > It should be possible to configure the pre-review job so at most N jobs > run > > at once. I think the rest will then properly queue up. > > > > On Mon, Apr 29, 2019 at 3:29 AM Laszlo Gaal <laszlo.g...@cloudera.com> > > wrote: > > > > > There was an unintended, errant review pushed to Impala's public Gerrit > > > instance, which resulted in about 30 review requests. This has also > > kicked > > > off a similar number of pre-review runs on jenkins.impala.io. > > > > > > I have personally verified the unintended nature of the problem with > the > > > owner. > > > > > > jenkins.impala.io is temporarily closed for builds until further > notice > > as > > > the fallout from the review storm is cleaned up. Once that is done, > I'll > > > send out the all clear signal when the service is restored. > > > > > > Apologies for the disruption, and thanks you for your patience. > > > > > > - Laszlo > > > > > >
