Martin Wille wrote:

Robert Ramey wrote:

...

Jeff Garland wrote:

...

...

Houston, we have a problem. [snip] It's a fact - running the bjam serialization test is going to consume 20 GB.

The disk requirements can be changed. Stripping the test binaries and removing the .o files already has been mentioned. Another chance lies in merging similar (in terms of instantiated templates) tests into one binary.

It might also be beneficial to allow finer grained results within a test file. Let's say I have a test file stl_containers.cpp that tests std::vector, std::list, etc. Now, if a compiler has a problem with one of these (e.g. std::map) - if I understand the regression test system correctly - it will mark this test as failed in the regression results and a user would assume that all the stl_containers would be unusable! What I would like is to be able to group sets of tests (like in the unit tests), but to show a breakdown of those tests (e.g. for std::vector, std::deque, etc.) so that if one of these groups fail, the user can see that specific container doesn't work for a perticular compiler/platform. Regards, Reece _________________________________________________________________ Express yourself with cool new emoticons http://www.msn.co.uk/specials/myemo