Vladimir Prus wrote:
No, because it's not bjam thing. The Boost.Build testsuite does include test/regression.py test that tests that non-zero return from a program is detected. It worked on windows a couple of weeks ago, and nothing was changed in that department since then. Can you reproduce this problem using a minimal testcase -- preferrably not using any of boost.serialization, or any non-standard assert functionality?
Hmmm - I would be happy to do this with something like: #include <cassert> int main(int argc, char * argv[]){ assert(false); } I thought it would be easy to name it assert-fail.cpp add to the directory which contains compile-fail.cpp etc. and add assert-fail to the Jamfile.v2 and rerun the test. But I found no such Jamfile.v2. So I'm not sure what to do with this. It's not at all clear to me how Boost.Build (as used for boost testing) is beiing tested aside from just running it on the trunk all the time. Robert Ramey