From: Aleksey Gurtovoy (agurtovoy_at_[hidden])
Date: 2004-09-26 05:00:34
Stefan Slapeta 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.
> What I know for sure is that this problem occurs independent of the OS
> and the machine (see the temporary 'slapeta_experimental' results) and
> whether the test is started by regression.py or not.
> The results for CW-9.3 seem to be correct now and thus there should be
> some more failing test cases for this toolset now.
> As for my Intel 8.0 results, I hope there are no similar interferences
> because they don't run without calling iclvars.bat once. I must
> manually make a testcase fail to verify this (before I fixed the tss
> cleanup, Intel failed, too, but this wasn't reported, either).
> That's where I am at the moment.
Stefan, thanks for pursuing this to the successful resolution!
-- Aleksey Gurtovoy MetaCommunications Engineering
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk