Stefan Slapeta <stefan@slapeta.com> writes:
After one day and one night of investigation, I think (!) I've finally managed to make bjam report correct results for my regressions.
As it seems, the solution is not calling cv_env.bat before running the test. This batch file is also called again before each test case and it seems that the environment gets somewhat confused then: during the execution of the cmd file the errorlevel is still set to 0 after the test case has been executed although the test case definitely reported something different.
Calling cw_env.bat may be needed in order to establish the PATH needed to find the C++ runtime DLLs. If you eliminated that call, maybe we need to find a way to do the same thing that doesn't mess up the errorlevel. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com