1 |
On Mon, Apr 5, 2010 at 9:15 AM, Paul Hartman |
2 |
<paul.hartman+gentoo@×××××.com> wrote: |
3 |
> On Sun, Apr 4, 2010 at 5:00 PM, Lie Ryan <lie.1296@×××××.com> wrote: |
4 |
>> I'm running with full system FEATURES="test" on, and I have a couple of |
5 |
>> programs that depended on dev-libs/boost. The boost testsuite always |
6 |
>> fails in my computer due to insufficient disk space, I usually simply |
7 |
>> skip the test for boost and just go on with the merge. But today, I |
8 |
>> decided to let the testsuite run to completion; so in preparation for |
9 |
>> that, I plugged in an external harddisk and made it so that |
10 |
>> /var/tmp/portage points to an empty disk image in the external harddrive. |
11 |
>> |
12 |
>> This setup works ok, and the testsuite is still running, however I saw |
13 |
>> now that the disk image's is now taking ~18 GB (and counting) while "du |
14 |
>> -sh" on /var/tmp/portage counted ~13GB. |
15 |
>> |
16 |
>> So, the question is, has anyone successfully compiled and run |
17 |
>> FEATURES="test" on boost and knows how much space the tests eat up in |
18 |
>> the end? |
19 |
>> |
20 |
>> I am suspecting of the possibility that maybe a testsuite gets into an |
21 |
>> infinite loop while writing a file or something constantly eats up |
22 |
>> diskspace. Or is it just that boost has an outrageously too extensive |
23 |
>> testsuite and it will turn out ok if I just left it to run. |
24 |
> |
25 |
> I'm trying it now, I have 64gb free in /var/tmp so I hope that's enough... :) |
26 |
> |
27 |
|
28 |
After almost 1.5 hours it is at its 22000th target and using 14G of |
29 |
/var/tmp so far... I'll keep waiting. |