|
|
Boost Testing : |
From: Doug Gregor (dgregor_at_[hidden])
Date: 2006-03-13 14:59:33
On Mar 13, 2006, at 9:55 AM, Vladimir Prus wrote:
> Doug Gregor wrote:
>
>> On Mar 10, 2006, at 2:11 AM, Vladimir Prus wrote:
>>> Doug,
>>> can you switch the OSL2 test runner to Boost.Build V2?
>>
>> Absolutely. I've just started a V2 regression test run now; we'll see
>> how everything goes in a couple of hours.
>
> The results are online now. There seems to be some V2-related
> failures in
> python and xpressive, the latter being very strange. Did you do
> just one
> clean run, or there were any issues?
No issues. I'm doing clean runs every night with V2.
> Probably another clean run will make the issues go away, otherwise
> I'd need
> to look closer.
>
>> Only one comment so far: I run 4 different sets of regression tests
>> on OSL machines, all of which run off my own user account. Does this
>> mean that I'll need to combine all of the configuration information
>> for the 4 regression testers into a single user-config.jam? It might
>> work, but sooner or later we're going to get a conflict. I expect
>> we'll need the ability to tell regression.py to use a specific user-
>> config.jam instead of the one in $HOME.
>
> Well, you can have adjust $HOME before starting regression.py.
> Anyway, when
> that becomes a real issue I'll devise some solution.
When I need to switch over another tester, I'll try that or tweak
BOOST_BUILD_PATH.
Doug