Daniel Schepler <[email protected]> writes: > HOME=/tmp/buildd/geda-gaf-1.8.2/tmp-home dh_auto_test > > At this point, the load average shoots through the roof, and top shows > a large number of make and sh processes being created. I therefore > have to interrupt the build.
I just spent some time playing around on an armhf system trying to figure out why geda-gaf won't build on armel|armhf. I see what's happening, and can confirm that it's happening on at least amd64 too... but it's only "fatal" on machines with constrained resources. It appears that 'make check' causes about 32k make processes to be spawned, then they're all reaped, then they're spawned again, and reaped again... then the tests are run. I haven't figured out what's causing this yet, but just leaving the build alone long enough will cause it to complete on any machine that doesn't doesn't exhaust resources trying to fork that many make processes twice in a row. My hack-around to allow geda-gaf to promote to testing is going to be to disable running the test suite on armel and armhf. But that's clearly not a real solution, so I'll leave this bug open until one of us has time to figure out what's going on and fix it for real... Bdale
pgpEYkPPWLc19.pgp
Description: PGP signature
