Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Reply-To: <gavin@16degrees.com.au>
From: "Gavin McDonald" <gavin@16degrees.com.au>
To: <builds@apache.org>
References: 
 <CAMopvkOrJmVSTueKXovWMYzVLu5K4hU5dP3_PfWK0=mJSmVKMw@mail.gmail.com>
 <528A8439.1050604@brondsema.net>
In-Reply-To: <528A8439.1050604@brondsema.net>
Subject: RE: Timeout limit doesn't work
Date: Tue, 19 Nov 2013 10:48:04 +1100
Organization: 16 degrees complete web solutions
Message-ID: <17fb801cee4b8$9ffce6f0$dff6b4d0$@16degrees.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQKdECdAYOkHjlhcqw42yJKiIP+F7gEqCuRSmIYAa6A=
Content-Language: en-au

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
>=20
> 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/
> >
>=20
> 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):
>=20
> https://builds.apache.org/job/Camel.trunk.notest/2041/
> 16hr, but timeout is 180 min
>=20
> https://builds.apache.org/job/Qpid-Java-Java-MMS-TestMatrix/1473/
> 11hr, but timeout is 180 min
>=20
> https://builds.apache.org/job/cloudstack-master-maven/3348/
> 6hr, timeout is elastic 150%
>=20
> https://builds.apache.org/job/Camel.trunk.fulltest/1615/
> 11hr, but timeout is 365 min
>=20
> https://builds.apache.org/job/river-qa-refactor-jdk7/113/
> 1.5hr (previous took 16hr), timeout is 2253 min -- really?
>=20
> https://builds.apache.org/job/Camel.2.12.x.fulltest/102/
> 11hr, but timeout is 365 min
>=20
> This ends up backlogging other jobs:
> https://builds.apache.org/label/ubuntu/load-statistics?type=3Dhour
>=20
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
>               <><