You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by Mike Percy <mp...@apache.org> on 2013/04/18 10:06:02 UTC
What's up with Jenkins?
Who knows what's going on with this thing?
Maven code 143 happens when the process gets killed but the last build was
running for only 26 mins. Our build timeout is set to 480 minutes (!) in
the Jenkins config.
Mike
Re: What's up with Jenkins?
Posted by Mike Percy <mp...@apache.org>.
Hmm strange. So I checked with someone who is a Jenkins committer and he
said that the build timeout plugin only takes into account active time, not
waiting time. Assuming that's true then this process killing stuff is still
a mystery.
Mike
On Thu, Apr 18, 2013 at 5:05 PM, Hari Shreedharan <hshreedharan@cloudera.com
> wrote:
> I added the !ubuntu6 - ubuntu6 was failing to clone the repo every single
> time. Not sure why.
>
> Hari
>
> --
> Hari Shreedharan
>
>
> On Thursday, April 18, 2013 at 5:03 PM, Mike Percy wrote:
>
> > Does anybody know why it is assigned to ubuntu && !ubuntu6? i.e. was
> there
> > a problem with ubuntu6?
> >
> > Hari good idea, worth checking on the wait time.
> >
> > Mike
> >
> >
> > On Thu, Apr 18, 2013 at 7:43 AM, Jarek Jarcec Cecho <jarcec@apache.org(mailto:
> jarcec@apache.org)>wrote:
> >
> > > We've been experiencing similar issue on Sqoop in recent past as well.
> I
> > > was able to google out that exit code 143 means SIGTERM signal.
> Additional
> > > googling has suggested that the signal might be sent by OOM killer,
> but as
> > > I do not have access to the physical boxes, I wasn't able to verify
> that.
> > > At least on Sqoop the issue "solved itself" in couple of days, so I
> wasn't
> > > pursuing it further lately.
> > >
> > > Jarcec
> > >
> > > On Thu, Apr 18, 2013 at 01:24:51AM -0700, Hari Shreedharan wrote:
> > > > Not sure if the wait time counts towards that timeout. If it does,
> then
> > >
> > > it is possible that it is getting killed because of that. I kept
> increasing
> > > the timeout each time I saw this happen.
> > > >
> > > >
> > > > Hari
> > > >
> > > > --
> > > > Hari Shreedharan
> > > >
> > > >
> > > > On Thursday, April 18, 2013 at 1:06 AM, Mike Percy wrote:
> > > >
> > > > > Who knows what's going on with this thing?
> > > > >
> > > > > Maven code 143 happens when the process gets killed but the last
> build
> > > was
> > > > > running for only 26 mins. Our build timeout is set to 480 minutes
> (!)
> > > >
> > >
> > > in
> > > > > the Jenkins config.
> > > > >
> > > > > Mike
>
>
Re: What's up with Jenkins?
Posted by Hari Shreedharan <hs...@cloudera.com>.
I added the !ubuntu6 - ubuntu6 was failing to clone the repo every single time. Not sure why.
Hari
--
Hari Shreedharan
On Thursday, April 18, 2013 at 5:03 PM, Mike Percy wrote:
> Does anybody know why it is assigned to ubuntu && !ubuntu6? i.e. was there
> a problem with ubuntu6?
>
> Hari good idea, worth checking on the wait time.
>
> Mike
>
>
> On Thu, Apr 18, 2013 at 7:43 AM, Jarek Jarcec Cecho <jarcec@apache.org (mailto:jarcec@apache.org)>wrote:
>
> > We've been experiencing similar issue on Sqoop in recent past as well. I
> > was able to google out that exit code 143 means SIGTERM signal. Additional
> > googling has suggested that the signal might be sent by OOM killer, but as
> > I do not have access to the physical boxes, I wasn't able to verify that.
> > At least on Sqoop the issue "solved itself" in couple of days, so I wasn't
> > pursuing it further lately.
> >
> > Jarcec
> >
> > On Thu, Apr 18, 2013 at 01:24:51AM -0700, Hari Shreedharan wrote:
> > > Not sure if the wait time counts towards that timeout. If it does, then
> >
> > it is possible that it is getting killed because of that. I kept increasing
> > the timeout each time I saw this happen.
> > >
> > >
> > > Hari
> > >
> > > --
> > > Hari Shreedharan
> > >
> > >
> > > On Thursday, April 18, 2013 at 1:06 AM, Mike Percy wrote:
> > >
> > > > Who knows what's going on with this thing?
> > > >
> > > > Maven code 143 happens when the process gets killed but the last build
> > was
> > > > running for only 26 mins. Our build timeout is set to 480 minutes (!)
> > >
> >
> > in
> > > > the Jenkins config.
> > > >
> > > > Mike
Re: What's up with Jenkins?
Posted by Mike Percy <mp...@apache.org>.
Does anybody know why it is assigned to ubuntu && !ubuntu6? i.e. was there
a problem with ubuntu6?
Hari good idea, worth checking on the wait time.
Mike
On Thu, Apr 18, 2013 at 7:43 AM, Jarek Jarcec Cecho <ja...@apache.org>wrote:
> We've been experiencing similar issue on Sqoop in recent past as well. I
> was able to google out that exit code 143 means SIGTERM signal. Additional
> googling has suggested that the signal might be sent by OOM killer, but as
> I do not have access to the physical boxes, I wasn't able to verify that.
> At least on Sqoop the issue "solved itself" in couple of days, so I wasn't
> pursuing it further lately.
>
> Jarcec
>
> On Thu, Apr 18, 2013 at 01:24:51AM -0700, Hari Shreedharan wrote:
> > Not sure if the wait time counts towards that timeout. If it does, then
> it is possible that it is getting killed because of that. I kept increasing
> the timeout each time I saw this happen.
> >
> >
> > Hari
> >
> > --
> > Hari Shreedharan
> >
> >
> > On Thursday, April 18, 2013 at 1:06 AM, Mike Percy wrote:
> >
> > > Who knows what's going on with this thing?
> > >
> > > Maven code 143 happens when the process gets killed but the last build
> was
> > > running for only 26 mins. Our build timeout is set to 480 minutes (!)
> in
> > > the Jenkins config.
> > >
> > > Mike
> >
>
Re: What's up with Jenkins?
Posted by Jarek Jarcec Cecho <ja...@apache.org>.
We've been experiencing similar issue on Sqoop in recent past as well. I was able to google out that exit code 143 means SIGTERM signal. Additional googling has suggested that the signal might be sent by OOM killer, but as I do not have access to the physical boxes, I wasn't able to verify that. At least on Sqoop the issue "solved itself" in couple of days, so I wasn't pursuing it further lately.
Jarcec
On Thu, Apr 18, 2013 at 01:24:51AM -0700, Hari Shreedharan wrote:
> Not sure if the wait time counts towards that timeout. If it does, then it is possible that it is getting killed because of that. I kept increasing the timeout each time I saw this happen.
>
>
> Hari
>
> --
> Hari Shreedharan
>
>
> On Thursday, April 18, 2013 at 1:06 AM, Mike Percy wrote:
>
> > Who knows what's going on with this thing?
> >
> > Maven code 143 happens when the process gets killed but the last build was
> > running for only 26 mins. Our build timeout is set to 480 minutes (!) in
> > the Jenkins config.
> >
> > Mike
>
Re: What's up with Jenkins?
Posted by Hari Shreedharan <hs...@cloudera.com>.
Not sure if the wait time counts towards that timeout. If it does, then it is possible that it is getting killed because of that. I kept increasing the timeout each time I saw this happen.
Hari
--
Hari Shreedharan
On Thursday, April 18, 2013 at 1:06 AM, Mike Percy wrote:
> Who knows what's going on with this thing?
>
> Maven code 143 happens when the process gets killed but the last build was
> running for only 26 mins. Our build timeout is set to 480 minutes (!) in
> the Jenkins config.
>
> Mike