[gentoo-user] Anyone ever emerged dev-libs/boost with FEATURES="test" and finished?

[Lie Ryan]

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.