David Abrahams-3 wrote:
Emil Dotchevski wrote:
I think Boost Exception is ready to be released but I wanted to confirm once again that I'm not missing something. Please bear with me I haven't released anything in Boost before. :)
Looking here:
http://www.boost.org/development/tests/trunk/developer/issues.html
There is a single msvc 8.0 failure for Boost Exception which I'm certain is because it's an incremental test. The library does work on msvc 8.
Why should an incremental test fail in this case? If you don't know, there's a mystery waiting to be uncovered and you shouldn't be so sure that it's a false positive in this case. If you do know, you should change your test so that it can work when run incrementally.
The RudbekAssociates-V2 runner is showing 2 sets of results for the throw_exception_test test: --- boost/bin.v2/libs/exception/test/throw_exception_test.test/msvc-8.0/debug/link-static/runtime-link-static --- boost/bin.v2/libs/exception/test/throw_exception_test.test/msvc-8.0/debug/threading-multi --- Where the 'link-static' version is failing and the other isn't. The exception jamfile used to specify <link>static, but doesnt any more, so is the 'failure' just because theres a set of old results lying around as well as the current ones? -- View this message in context: http://www.nabble.com/-1.36.0--RELEASE-BRANCH-OPEN-FOR-BUG-FIXES-tp18078659p... Sent from the Boost - Dev mailing list archive at Nabble.com.