Jenkins alive?

[Till Westmann <ti...@apache.org>]

Hi,

Abdullah has restored a change on Gerrit [1], however, Jenkins doesn’t 
seem to pick it up.
I’ve also tried to trigger Jenkins manually, but that didn’t help 
either (so far …).

Does anybody know what’s up?

Cheers,
Till

[1] https://asterix-gerrit.ics.uci.edu/#/c/529/

Re: Jenkins alive?

[Steven Jacobs <sj...@ucr.edu>]

My new patch set isn't trying to build either.
Steven

On Sat, Jan 16, 2016 at 2:08 PM, Ian Maxon <im...@uci.edu> wrote:

> I made it set to abort after 5hrs so hopefully that will do the trick, but
> I'll have to be careful as the stress tests are intended to take a long
> time in the first place.
>
> On Sat, Jan 16, 2016 at 1:32 PM, Murtadha Hubail <hu...@gmail.com>
> wrote:
>
> > It seems the issue is back again.
> >
> > -Murtadha
> >
> > > On Jan 14, 2016, at 8:42 AM, Ian Maxon <im...@uci.edu> wrote:
> > >
> > > It's just the stress testing build again. It should be fine now.
> > >
> > > On Thu, Jan 14, 2016 at 12:36 AM, abdullah alamoudi <
> bamousaa@gmail.com>
> > > wrote:
> > >
> > >> It seems like Jenkins has died again or something. My changes don't
> > build
> > >> at all.
> > >>
> > >> Cheers,
> > >> Abdullah.
> > >>
> > >> Amoudi, Abdullah.
> > >>
> > >> On Mon, Jan 4, 2016 at 9:16 PM, Ian Maxon <im...@uci.edu> wrote:
> > >>
> > >>> Should be fixed at least temporarily for now. The error was that the
> > >>> new stress testing job was keeping the backup from running, and when
> > >>> the backup is waiting to shut Jenkins down, it doesn't allow any new
> > >>> jobs to enter the queue. I'll have to see about the timing of the
> > >>> stress test to make sure it won't interfere with the backups.
> > >>>
> > >>> On Mon, Jan 4, 2016 at 7:25 AM, Till Westmann <ti...@apache.org>
> > wrote:
> > >>>> Hi,
> > >>>>
> > >>>> Abdullah has restored a change on Gerrit [1], however, Jenkins
> doesn’t
> > >>> seem
> > >>>> to pick it up.
> > >>>> I’ve also tried to trigger Jenkins manually, but that didn’t help
> > >> either
> > >>> (so
> > >>>> far …).
> > >>>>
> > >>>> Does anybody know what’s up?
> > >>>>
> > >>>> Cheers,
> > >>>> Till
> > >>>>
> > >>>> [1] https://asterix-gerrit.ics.uci.edu/#/c/529/
> > >>>
> > >>
> >
> >
>

Re: Jenkins alive?

[Ian Maxon <im...@uci.edu>]

I made it set to abort after 5hrs so hopefully that will do the trick, but
I'll have to be careful as the stress tests are intended to take a long
time in the first place.

On Sat, Jan 16, 2016 at 1:32 PM, Murtadha Hubail <hu...@gmail.com>
wrote:

> It seems the issue is back again.
>
> -Murtadha
>
> > On Jan 14, 2016, at 8:42 AM, Ian Maxon <im...@uci.edu> wrote:
> >
> > It's just the stress testing build again. It should be fine now.
> >
> > On Thu, Jan 14, 2016 at 12:36 AM, abdullah alamoudi <ba...@gmail.com>
> > wrote:
> >
> >> It seems like Jenkins has died again or something. My changes don't
> build
> >> at all.
> >>
> >> Cheers,
> >> Abdullah.
> >>
> >> Amoudi, Abdullah.
> >>
> >> On Mon, Jan 4, 2016 at 9:16 PM, Ian Maxon <im...@uci.edu> wrote:
> >>
> >>> Should be fixed at least temporarily for now. The error was that the
> >>> new stress testing job was keeping the backup from running, and when
> >>> the backup is waiting to shut Jenkins down, it doesn't allow any new
> >>> jobs to enter the queue. I'll have to see about the timing of the
> >>> stress test to make sure it won't interfere with the backups.
> >>>
> >>> On Mon, Jan 4, 2016 at 7:25 AM, Till Westmann <ti...@apache.org>
> wrote:
> >>>> Hi,
> >>>>
> >>>> Abdullah has restored a change on Gerrit [1], however, Jenkins doesn’t
> >>> seem
> >>>> to pick it up.
> >>>> I’ve also tried to trigger Jenkins manually, but that didn’t help
> >> either
> >>> (so
> >>>> far …).
> >>>>
> >>>> Does anybody know what’s up?
> >>>>
> >>>> Cheers,
> >>>> Till
> >>>>
> >>>> [1] https://asterix-gerrit.ics.uci.edu/#/c/529/
> >>>
> >>
>
>

Re: Jenkins alive?

[Murtadha Hubail <hu...@gmail.com>]

It seems the issue is back again.

-Murtadha

> On Jan 14, 2016, at 8:42 AM, Ian Maxon <im...@uci.edu> wrote:
> 
> It's just the stress testing build again. It should be fine now.
> 
> On Thu, Jan 14, 2016 at 12:36 AM, abdullah alamoudi <ba...@gmail.com>
> wrote:
> 
>> It seems like Jenkins has died again or something. My changes don't build
>> at all.
>> 
>> Cheers,
>> Abdullah.
>> 
>> Amoudi, Abdullah.
>> 
>> On Mon, Jan 4, 2016 at 9:16 PM, Ian Maxon <im...@uci.edu> wrote:
>> 
>>> Should be fixed at least temporarily for now. The error was that the
>>> new stress testing job was keeping the backup from running, and when
>>> the backup is waiting to shut Jenkins down, it doesn't allow any new
>>> jobs to enter the queue. I'll have to see about the timing of the
>>> stress test to make sure it won't interfere with the backups.
>>> 
>>> On Mon, Jan 4, 2016 at 7:25 AM, Till Westmann <ti...@apache.org> wrote:
>>>> Hi,
>>>> 
>>>> Abdullah has restored a change on Gerrit [1], however, Jenkins doesn’t
>>> seem
>>>> to pick it up.
>>>> I’ve also tried to trigger Jenkins manually, but that didn’t help
>> either
>>> (so
>>>> far …).
>>>> 
>>>> Does anybody know what’s up?
>>>> 
>>>> Cheers,
>>>> Till
>>>> 
>>>> [1] https://asterix-gerrit.ics.uci.edu/#/c/529/
>>> 
>> 

Re: Jenkins alive?

[Ian Maxon <im...@uci.edu>]

It's just the stress testing build again. It should be fine now.

On Thu, Jan 14, 2016 at 12:36 AM, abdullah alamoudi <ba...@gmail.com>
wrote:

> It seems like Jenkins has died again or something. My changes don't build
> at all.
>
> Cheers,
> Abdullah.
>
> Amoudi, Abdullah.
>
> On Mon, Jan 4, 2016 at 9:16 PM, Ian Maxon <im...@uci.edu> wrote:
>
> > Should be fixed at least temporarily for now. The error was that the
> > new stress testing job was keeping the backup from running, and when
> > the backup is waiting to shut Jenkins down, it doesn't allow any new
> > jobs to enter the queue. I'll have to see about the timing of the
> > stress test to make sure it won't interfere with the backups.
> >
> > On Mon, Jan 4, 2016 at 7:25 AM, Till Westmann <ti...@apache.org> wrote:
> > > Hi,
> > >
> > > Abdullah has restored a change on Gerrit [1], however, Jenkins doesn’t
> > seem
> > > to pick it up.
> > > I’ve also tried to trigger Jenkins manually, but that didn’t help
> either
> > (so
> > > far …).
> > >
> > > Does anybody know what’s up?
> > >
> > > Cheers,
> > > Till
> > >
> > > [1] https://asterix-gerrit.ics.uci.edu/#/c/529/
> >
>

Re: Jenkins alive?

[abdullah alamoudi <ba...@gmail.com>]

It seems like Jenkins has died again or something. My changes don't build
at all.

Cheers,
Abdullah.

Amoudi, Abdullah.

On Mon, Jan 4, 2016 at 9:16 PM, Ian Maxon <im...@uci.edu> wrote:

> Should be fixed at least temporarily for now. The error was that the
> new stress testing job was keeping the backup from running, and when
> the backup is waiting to shut Jenkins down, it doesn't allow any new
> jobs to enter the queue. I'll have to see about the timing of the
> stress test to make sure it won't interfere with the backups.
>
> On Mon, Jan 4, 2016 at 7:25 AM, Till Westmann <ti...@apache.org> wrote:
> > Hi,
> >
> > Abdullah has restored a change on Gerrit [1], however, Jenkins doesn’t
> seem
> > to pick it up.
> > I’ve also tried to trigger Jenkins manually, but that didn’t help either
> (so
> > far …).
> >
> > Does anybody know what’s up?
> >
> > Cheers,
> > Till
> >
> > [1] https://asterix-gerrit.ics.uci.edu/#/c/529/
>

Re: Jenkins alive?

[Ian Maxon <im...@uci.edu>]

Should be fixed at least temporarily for now. The error was that the
new stress testing job was keeping the backup from running, and when
the backup is waiting to shut Jenkins down, it doesn't allow any new
jobs to enter the queue. I'll have to see about the timing of the
stress test to make sure it won't interfere with the backups.

On Mon, Jan 4, 2016 at 7:25 AM, Till Westmann <ti...@apache.org> wrote:
> Hi,
>
> Abdullah has restored a change on Gerrit [1], however, Jenkins doesn’t seem
> to pick it up.
> I’ve also tried to trigger Jenkins manually, but that didn’t help either (so
> far …).
>
> Does anybody know what’s up?
>
> Cheers,
> Till
>
> [1] https://asterix-gerrit.ics.uci.edu/#/c/529/