Roland Schwarz <roland.schwarz@chello.at> writes:
Joaquín Mª López Muñoz wrote:
* The "speedsnail" regression runner has some peculiarities: 1. It builds the tests in release mode (although it gives no indication of this in the toolset names used) This seems to cause problems with some facilities from Boost.Test.
The speedsnail-dbg is the debugging version and the speedsnail is the release version. Can you point me to where the test is causing trouble? Are you speaking about the Internal Compiler Faults ? This already should be fixed.
There was an extensive discussion about this on the testing list a couple of months ago, when I started running release mode tests. Certain things break in release mode (compare your release mode results to the debug mode results --- there are lots more red boxes). The compromise we came to was that I would run release mode tests, but tag all the toolsets with ~release so they could be identified as such, and failures would not appear in the regression report emails. Historically, release mode tests have not been run, so release mode failures are not necessarily "regressions" --- the same test might have failed in release mode with previous boost releases. My user-config.jam is: using python : 2.5 : c:/local/python25 ; using msvc : 6.5 : c:/progra~1/micros~3/vc98/bin/cl.exe ; using msvc : all ; using gcc : 3.4.0 : c:/local/mingw/bin/g++.exe ; using borland : 5.8.2 : c:/progra~1/borland/bds/4.0/bin/bcc32.exe ; using msvc : 6.5~release : c:/progra~1/micros~3/vc98/bin/cl.exe ; using msvc : 7.1~release : c:/local/vc71/bin/cl.exe ; using msvc : 8.0express~release : c:/progra~1/MID05A~1/vc/bin/cl.exe ; using gcc : 3.4.0~release : "c:/local/mingw/bin/g++.exe" ; using borland : 5.8.2~release : c:/progra~1/borland/bds/4.0/bin/bcc32.exe ; Anthony -- Anthony Williams Just Software Solutions Ltd - http://www.justsoftwaresolutions.co.uk Registered in England, Company Number 5478976. Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL