Bug#785651: glibc: test run times out on ci.debian.net; maybe don't force a build every time
* Paul Gevers:
> On Sun, 01 Apr 2018 21:56:33 +0200 Florian Weimer <fw@deneb.enyo.de> wrote:
>> > I have no idea. On a fast 4-cores amd64 machine and for the 3 flavours
>> > built on amd64, the glibc takes around 20 minutes to build and the
>> > testsuite around 2h to run.
>>
>> This is still rather slow. I see native builds on relatively current
>> hardware taking 2 minutes, plus 12 to 15 minutes to build and run the
>> test suite (all with parallel make, although parallel make for tests
>> is disabled automatically for some subdirectories). 200 minutes on
>> current (amd64) hardware sounds quite excessive.
>
> I just did a retry on our infrastructure and it ran in 57 minutes. But
> it ran on one of the two big workers (8 cores and 30 GB memory). We want
> to make all workers equal and we are going down to 2 cores and 7.2 GB.
>
> Could it be that the memory is the actual problem and/or also an issue?
I looked at the build process, and the amd64 package actually builds
glibc three times (for amd64, i386 and x32). So 57 minutes is
actually very close to the numbers I gave.
I'm not sure why it is necessary to build glibc three times (unless
it's impossible to get multi-arch packages into the buildroot). If
you disable kernel support for the i386 and x32 subarchitectures, at
those test suites will not run, which will speed up the build
somewhat.
Reply to: