Regression: avoid cleanup of binaries
After the regression tests there seems to be a total cleanup of the binaries. Is it possible to avoid this in some way? (maybe specifying --incremental is the solution, but I would rather guess letting away this option should clean up the binaries _before_ the test run, shouldn't it?!?) Stefan
Stefan Slapeta wrote:
After the regression tests there seems to be a total cleanup of the binaries. Is it possible to avoid this in some way? (maybe specifying --incremental is the solution, but I would rather guess letting away this option should clean up the binaries _before_ the test run, shouldn't it?!?)
That cleanup is not supposed to be "total". The test system will remove binaries which have been tested with success. This procedure is required in order to keep the total size of all test binaries within reasonable limits. Regards, m
Martin Wille wrote:
That cleanup is not supposed to be "total". The test system will remove binaries which have been tested with success.
This procedure is required in order to keep the total size of all test binaries within reasonable limits.
This care about my disk space is very obliging. Nevertheless, if I kindly ask, is there an easy way to avoid this? I've a list of test cases which behave _very_ strangly (GPF, obviously incorrect exit code, ...) without reflecting this in the test results, and it seems the time has come now to have a look at this. Anyway, do you know an easy way to manually build a single test case? Stefan
Stefan Slapeta <stefan@slapeta.com> writes:
Martin Wille wrote:
That cleanup is not supposed to be "total". The test system will remove binaries which have been tested with success. This procedure is required in order to keep the total size of all test binaries within reasonable limits.
This care about my disk space is very obliging. Nevertheless, if I kindly ask, is there an easy way to avoid this? I've a list of test cases which behave _very_ strangly (GPF, obviously incorrect exit code, ...) without reflecting this in the test results, and it seems the time has come now to have a look at this.
Add --preserve-test-targets to the bjam command line and they won't be removed.
Anyway, do you know an easy way to manually build a single test case?
bjam name-of-test -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
Stefan Slapeta wrote:
This care about my disk space is very obliging.
Actually, this is care about *my* disk space. Nevertheless, if I
kindly ask, is there an easy way to avoid this? I've a list of test cases which behave _very_ strangly (GPF, obviously incorrect exit code, ...) without reflecting this in the test results, and it seems the time has come now to have a look at this.
Anyway, do you know an easy way to manually build a single test case?
cd into the respective test directory, then bjam -sTOOLSSET testname Regards, m
participants (3)
-
David Abrahams -
Martin Wille -
Stefan Slapeta