Boost Testing :
Subject: Re: [Boost-testing] Trunk testing (general) and MSVC11
From: Christoph Macheiner (christoph.macheiner_at_[hidden])
Date: 2012-08-27 10:48:53
"Eric Niebler" <eric_at_[hidden]> wrote in message
> On 8/24/2012 1:00 PM, Steven Watanabe wrote:
>> On 08/24/2012 12:39 PM, Eric Niebler wrote:
>>> I'm guessing
>>> most of the space is debug information. Is there a way to turn that off?
>> Add <debug-symbols>off to the requirements.
> Done. Thanks, Steven. test_actions.obj alone goes from 63Mb to 12Mb.
> Many of the other .obj files are also dramatically smaller. This easily
> outweighs the extra build of the test framework that it requires, which
> only takes up 22Mb.
Imho, <debug-symbols>off is not the solution to this issue. There is a
"RmTemps" jam rule that is called after each test, but it only deletes the
.exe, and leaves the rest of the build output (why it is done like this I
have no clue). I'd say everything should be built with debug-symbols (to be
able to debug failures), and the RmTemps rule should probably delete the
complete build output on success, and leave everything in case of a failure.
Of course, this might require more changes other than to the RmTemps rule
alone (and I have no idea how to achieve this). Anybody know how to do this?
This would reduce the disk usage to "almost nothing", during the run as well
Also useful would be not to do a svn checkout but a svn export in case I
don't plan to commit any changes (which most probably is the default). This
would save half the disk space of the sources (and also time, given Windows'
filesystem (un)performance). I could do this on my own and run
with --have-source, but it's easy to implement in regression.py and I don't
know what other side-effects the --have-source switch has (if any).
BTW: The disk space used after my Friday run (so before Eric's change) is
almost exactly 50gb and the run took about 3:10 hours with 8 concurrent bjam