hi all, i'm not sure what is the reason for this, but the boost.heap testsuite has some severe problems, which seem to be related with boost.test: in the release branch, all (!!!) tests fail on all unixy platforms. this was not the case when i developed the library. and i've reported this issue more than once. well, using a testing framework, which crashes before the test cases are even executed is a bit, well, worrying. iac, i was happy that the tests in the release branch used to work at least ... however i am seeing a lot of messages like: Assertion failed: (!!s_active_handler), function jump_buffer, file ../boost/test/impl/execution_monitor.ipp, line 683. Assertion failed: (!!s_active_handler), function sys_sig, file ../boost/test/impl/execution_monitor.ipp, line 690. what does this tell me? thnx, tim
Tim Blechmann
hi all, i'm not sure what is the reason for this, but the boost.heap testsuite has some severe problems, which seem to be related with boost.test:
in the release branch, all (!!!) tests fail on all unixy platforms. this
I did not make any changes in release branch. Did anyone else do?
Assertion failed: (!!s_active_handler), function jump_buffer, file ../boost/test/impl/execution_monitor.ipp, line 683. Assertion failed: (!!s_active_handler), function sys_sig, file ../boost/test/impl/execution_monitor.ipp, line 690.
what does this tell me?
Bad build? New compilation options? There is an assert in Boost.Test code, which is failing, but I do not see how this failure can happen. Gennadiy
Assertion failed: (!!s_active_handler), function jump_buffer, file ../boost/test/impl/execution_monitor.ipp, line 683. Assertion failed: (!!s_active_handler), function sys_sig, file ../boost/test/impl/execution_monitor.ipp, line 690.
what does this tell me?
Bad build? New compilation options?
that was it, bad linking options actually! boost.test was linked twice, leading to this more than awkward behavior ...
participants (2)
-
Gennadiy Rozental
-
Tim Blechmann