river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Mason ...@jmason.org>
Subject Re: Summarily killing stuck builds
Date Fri, 08 Jan 2010 16:12:58 GMT
It may be worthwhile using the long-running build lock, too.
(see 'Are there recommended or mandatory Hudson settings for ASF
projects?' on the hudson wiki page)

--j.

On Fri, Jan 8, 2010 at 15:06, sebb <sebbaz@gmail.com> wrote:
> Another stuck build:
>
> http://hudson.zones.apache.org/hudson/job/River-trunk/221/
> Started 2 days 2 hr ago
> on vesta.apache.org (Ubuntu)
>
> Previous builds seem to take around 3 hours, so I have set the build
> timeout to 5 hours (300 mins)
>
> On 31/12/2009, Tim Ellison <t.p.ellison@gmail.com> wrote:
>> FYI
>>
>>  I am continuing to kill builds that run for long periods without making
>>  progress (e.g. [1]).
>>
>>  In each case, I also go into the build configuration and set the flag to
>>  kill stuck builds after 120 mins.
>>
>>  It would be helpful if people set this timeout to a reasonable value for
>>   their project when creating new builds.
>>
>>  [1] Recent stuck builds:
>>  http://hudson.zones.apache.org/hudson/job/Synapse%20-%201.3%20-%20SNAPSHOT/186/
>>  http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/1595/
>>  http://hudson.zones.apache.org/hudson/job/HBase-Patch/1052/
>>
>>  Regards,
>>
>> Tim
>>
>
>



-- 
--j.

Mime
View raw message