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
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
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
Hi,
I am an active porter for the alpha architecture in that I run two
buildd servers and I intend to continue this for the lifetime of the
jessie release:
For alpha, I
- test some packages on this architecture
- maintain buildds
I am not a DD/DM
Bill MacAllister
--
Bill MacAllister
In
Hello,
I am not currently a porter but I would like to be one for the
architectures ppc64 and sparc64.
I currently have no hardware, but I will be obtaining ppc64 and sparc64
systems in the very near future (within 2 weeks).
I do have advanced C knowledge and have programmed
for 12 years. I have
Hi,
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the jessie release:
For SPARC64, I
- test a lot of the packages for KDE4 Desktop
- testing and currently preparing patches for Iceweasel
- test Vanilla build of the Linux kern
6 matches
Mail list logo
