So currently all of the armel PPA buildds that are in auto-mode on production launchpad are using qemu-arm-static to run their build chroots.
On staging I saw a dramatic decrease in the number of OOM-type failures and catastrophic mmap() failures, with a slight uptick in sig11s (on different packages, and hard to reproduce via re-builds). We decided it was Good Enough For Now and moved things into production.
Probably the best way to stress-test this now would be to run a bunch of armel PPA builds through production launchpad (say, a precise main rebuild or something) and examine the build failures. We definitely felt that this patch gave a worthwhile improvement over the old behavior.
So currently all of the armel PPA buildds that are in auto-mode on production launchpad are using qemu-arm-static to run their build chroots.
On staging I saw a dramatic decrease in the number of OOM-type failures and catastrophic mmap() failures, with a slight uptick in sig11s (on different packages, and hard to reproduce via re-builds). We decided it was Good Enough For Now and moved things into production.
Probably the best way to stress-test this now would be to run a bunch of armel PPA builds through production launchpad (say, a precise main rebuild or something) and examine the build failures. We definitely felt that this patch gave a worthwhile improvement over the old behavior.