Re: [boost] testers blocked after changeset 85924 in trunk.

Subject: Re: [boost] testers blocked after changeset 85924 in trunk.
From: Sergey Cheban (s.cheban_at_[hidden])
Date: 2013-10-01 12:51:41

On 28.09.2013 4:59, Vicente J. Botet Escriba wrote:

> the last change set that has been taken in account in trunk regression
> test is 85924.
>
> I'm expecting a lot of testers to cycle.
>
> Note that release regressing test are not blocked.
> Could someone explain what is happening?
I see the following in the log:

C:\Users\BoostTest\Trunk\boost\status>"C:\Users\BoostTest\Trunk\tools_bjam\bin.ntx86\bjam.exe" 
"-sBOOST_BUILD_PATH=C:\Users\BoostTest\Trunk;C:\Users\BoostTest\Trunk\tools_bb" 
"-sBOOST_ROOT=C:\Users\BoostTest\Trunk\boost" 
"--boost=C:\Users\BoostTest\Trunk\boost" 
"--boost-build=C:\Users\BoostTest\Trunk\tools_bb" 
"--debug-configuration"  -l300 toolset=msvc-9.0,msvc-10.0,msvc-11.0 -d2 
preserve-test-targets=off --dump-tests --abbreviate-paths -j 16 
address-model=32 "--build-dir=C:\Users\BoostTest\Trunk\results" 
1>>"C:\Users\BoostTest\Trunk\results\bjam.log" 2>&1
# Running Boost.Build tests
Traceback (most recent call last):
   File "run.py", line 60, in <module>
     runner(root)
   File "C:\Users\BoostTest\Trunk\tools_regression_src\regression.py", 
line 205, in __init__
     self.main()
   File "C:\Users\BoostTest\Trunk\tools_regression_src\regression.py", 
line 566, in main
     getattr(self,action_m)()
   File "C:\Users\BoostTest\Trunk\tools_regression_src\regression.py", 
line 531, in command_regression
     self.command_test()
   File "C:\Users\BoostTest\Trunk\tools_regression_src\regression.py", 
line 329, in command_test
     self.command_test_boost_build()
   File "C:\Users\BoostTest\Trunk\tools_regression_src\regression.py", 
line 369, in command_test_boost_build
     "boost/bin.v2/libs/any/test/any_test.test"));
WindowsError: [Error 3] The system cannot find the path specified: 
'C:\\Users\\BoostTest\\Trunk\\results\\boost/bin.v2/libs/any/test/any_test.test/*.*'

Unfortunately, the Trunk\results\bjam.log has already been deleted and I 
cannot look into it.

-- 
Sergey Cheban