Hi all, On Sat, 4 Aug 2018 18:48:44 +0200 Aurelien Jarno <aurelien@aurel32.net> wrote: > On 2018-07-23 22:17, Paul Gevers wrote: > > 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 don't think think the memory is really a problem, at least not for the > values you give. A few tests might be memory hungry, but 4GB should be > enough. I retried another time, now that all the workers are equivalent. The current test suite runs in around 2:10 on our infrastructure. Albeit long, I will remove glibc from the blacklist. However, we would still appreciate it when the test can be made smarter. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature