www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin McDonald" <ga...@16degrees.com.au>
Subject RE: Timeout limit doesn't work
Date Mon, 18 Nov 2013 23:48:04 GMT
Olivier Lamy upgraded the Jenkins instance, he seemed to recall a fix for this.

Let's see how it runs now.

Thanks

Gav...

> -----Original Message-----
> From: Dave Brondsema [mailto:dave@brondsema.net]
> Sent: Tuesday, 19 November 2013 8:19 AM
> To: builds@apache.org
> Subject: Re: Timeout limit doesn't work
> 
> On 11/14/13 2:14 PM, Lukasz Lenart wrote:
> > Why the Absolute Timeout limit doesn't work? For example, the build
> > [1] has timeout limit set to 187 minutes, but that job [1] is running
> > 15h as for now and blocks other builds :\
> >
> > https://builds.apache.org/job/CXF-2.7-deploy/configure
> > https://builds.apache.org/job/CXF-2.7-deploy/219/
> >
> 
> I'm seeing this as a real problem, too.  Looking at jobs currently running on
> the ubuntu hosts, these seem very very long (and still going, as of this
> writing):
> 
> https://builds.apache.org/job/Camel.trunk.notest/2041/
> 16hr, but timeout is 180 min
> 
> https://builds.apache.org/job/Qpid-Java-Java-MMS-TestMatrix/1473/
> 11hr, but timeout is 180 min
> 
> https://builds.apache.org/job/cloudstack-master-maven/3348/
> 6hr, timeout is elastic 150%
> 
> https://builds.apache.org/job/Camel.trunk.fulltest/1615/
> 11hr, but timeout is 365 min
> 
> https://builds.apache.org/job/river-qa-refactor-jdk7/113/
> 1.5hr (previous took 16hr), timeout is 2253 min -- really?
> 
> https://builds.apache.org/job/Camel.2.12.x.fulltest/102/
> 11hr, but timeout is 365 min
> 
> This ends up backlogging other jobs:
> https://builds.apache.org/label/ubuntu/load-statistics?type=hour
> 
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
>               <><


Mime
View raw message