On 04-09-13 14:04, Finn Thain wrote:
>
> On Wed, 4 Sep 2013, Thorsten Glaser wrote:
>
>> Eric Dorland dixit:
>>
testing message digests takes too long on this slow platform (I
noticed that as I ran top on the buildd while upgrading its chroot
basedir) and builds are killed after
Finn Thain dixit:
>How about a test for actual inactivity? (E.g. processes blocked for too
>long, or process cumulative CPU time not accumulating.)
>
>Or just make the timeout adjustable or optional. When was the last time
The timeout is a feature of the buildd software we cannot disable.
>you
On Wed, 4 Sep 2013, Thorsten Glaser wrote:
> Eric Dorland dixit:
>
> >> testing message digests takes too long on this slow platform (I
> >> noticed that as I ran top on the buildd while upgrading its chroot
> >> basedir) and builds are killed after inactivity for a while
>
> >Well that's a s
Eric Dorland dixit:
>> testing message digests takes too long on this
>> slow platform (I noticed that as I ran top on
>> the buildd while upgrading its chroot basedir)
>> and builds are killed after inactivity for a while
>Well that's a shame. Any suggestions?
Only the really unconstructive one
4 matches
Mail list logo
