No need to try anything else. I'll see if I can fix the problem. The option is a new one I added this week to try and reduce testing hard drive space. On Jun 15, 2014 12:46 PM, "John Maddock" wrote:

Could you try locally and add the "--remove-test-targets" option?

...

I've been trying, but regression.py bombs out for me in:

self.git_command( 'submodule foreach', '"git reset --quiet --hard; git clean -fxd"')

Git complains it doesn't understand "--hard;" - note the semi-colon. This is under the windows command prompt. I've just submitted a pull request to tentatively fix this, but how do I run the script locally without the remote version getting downloaded and overwriting my changes?

In any event you put your finger right on the issue - running bjam with the --remove-test-targets option results in the same failures I see online. Any idea what's changed?

Many thanks, John.

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/ mailman/listinfo.cgi/boost

No need to try anything else. I'll see if I can fix the problem. The option is a new one I added this week to try and reduce testing hard drive space.

Any progress on this? I can obviously disable things like pre-compiled-headers and fix things that way, but that feels like the wrong fix to me (longer compile times etc). Thanks, John.

...

Could you try locally and add the "--remove-test-targets" option?

...

I've been trying, but regression.py bombs out for me in:

self.git_command( 'submodule foreach', '"git reset --quiet --hard; git clean -fxd"')

Git complains it doesn't understand "--hard;" - note the semi-colon. This is under the windows command prompt. I've just submitted a pull request to tentatively fix this, but how do I run the script locally without the remote version getting downloaded and overwriting my changes?

In any event you put your finger right on the issue - running bjam with the --remove-test-targets option results in the same failures I see online. Any idea what's changed?

Many thanks, John.

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/ mailman/listinfo.cgi/boost

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

...

No need to try anything else. I'll see if I can fix the problem. The option

...

is a new one I added this week to try and reduce testing hard drive space.

Any progress on this?

I can obviously disable things like pre-compiled-headers and fix things that way, but that feels like the wrong fix to me (longer compile times etc).

Thanks, John.

The --remove-test-targets bjam option seems to have shrunk things down a bit. I'm not hitting the size limit anymore. It looks like we're down to 30GB/compiler from 60GB.

This solved my problem, but if we could have less churn on keeping unnecessary object files, tests would run quicker (I believe that they are usually disk IO limited, especially on windows). I'm not sure what if any other solutions there are to this.

For the time being I've disabled PCH support in Boost.Math when --remove-test-targets is on the command line. Hopefully we'll actually get some regression test results now at the expense of even slower build times. This is still the wrong fix though: we shouldn't break a documented feature (PCH) with an undocumented one. John.