On Mon, Apr 5, 2010 at 10:53 AM, Paul Hartman <[email protected]> wrote: > On Mon, Apr 5, 2010 at 9:15 AM, Paul Hartman > <[email protected]> wrote: >> On Sun, Apr 4, 2010 at 5:00 PM, Lie Ryan <[email protected]> wrote: >>> I'm running with full system FEATURES="test" on, and I have a couple of >>> programs that depended on dev-libs/boost. The boost testsuite always >>> fails in my computer due to insufficient disk space, I usually simply >>> skip the test for boost and just go on with the merge. But today, I >>> decided to let the testsuite run to completion; so in preparation for >>> that, I plugged in an external harddisk and made it so that >>> /var/tmp/portage points to an empty disk image in the external harddrive. >>> >>> This setup works ok, and the testsuite is still running, however I saw >>> now that the disk image's is now taking ~18 GB (and counting) while "du >>> -sh" on /var/tmp/portage counted ~13GB. >>> >>> So, the question is, has anyone successfully compiled and run >>> FEATURES="test" on boost and knows how much space the tests eat up in >>> the end? >>> >>> I am suspecting of the possibility that maybe a testsuite gets into an >>> infinite loop while writing a file or something constantly eats up >>> diskspace. Or is it just that boost has an outrageously too extensive >>> testsuite and it will turn out ok if I just left it to run. >> >> I'm trying it now, I have 64gb free in /var/tmp so I hope that's enough... :) >> > > After almost 1.5 hours it is at its 22000th target and using 14G of > /var/tmp so far... I'll keep waiting. >
It finished, successfully. 1 hour 52 minutes (normal compile of boost without testing takes about 3 minutes). Peak disk usage was about 20G when i spot-checked... The ebuild checks for 1024M free, maybe they need to change that to check for 20G if testing?
