|
|
Boost Testing : |
From: David Abrahams (dave_at_[hidden])
Date: 2007-02-06 12:45:08
"Misha Berga;" <mbergal_at_[hidden]> writes:
> David Abrahams wrote:
>> Take a look at http://tinyurl.com/35x9p6
>> (http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/output/BoostConsulting-boost-bin-v2-libs-algorithm-string-test-replace-test-msvc-8-0-m-rls-adrs-mdl-64-instr-set-optrn-thrd-mlt.html).
>>
>> It appears that the test succeeded but the reporting tools are saying
>> that it failed (?)
>>
>
> David,
>
> Could you send us whole bjam.log for your first run.
I can send the one I have lying around at the moment. I don't know
whether that's the "first run". Done as
BoostConsulting-20070206-bjam.log
> In case you don't have it, would it be too much to ask you to get
> the latest regression.py
> add --send-bjam-log to command line
Are you not updating regression.py on the branch? That might explain
why I'm not ending up with the latest. The one I have only has a
--dont-send-logs option. IIRC regression.py tries to update itself
from the downloaded source during the update-self phase. I think
maybe either you need to separately update it from the HEAD or make
sure you keep the RC branch in synch.
Hmm, even on HEAD I don't see --send-bjam-log. What's up?
> and rerun the full cycle
> (sorry)
What does that mean? A clean run from the beginning?
-- Dave Abrahams Boost Consulting www.boost-consulting.com