Re: [boost] [Boost.any] Nightly trunk testing failures

Subject: Re: [boost] [Boost.any] Nightly trunk testing failures
From: K. Noel Belcourt (kbelco_at_[hidden])
Date: 2009-04-28 13:00:04

On Apr 28, 2009, at 10:45 AM, Vladimir Prus wrote:

> K. Noel Belcourt wrote:
>>
>> Most nightly trunk testing results are failing with this error
>> message.  Have their been recent changes to Boost.any that could have
>> caused this?
>>
>> # Making "/var/scratch/boost/results" directory...
>> # Starting tests ("/var/scratch/boost/tools_bjam/bin.linuxx86/ 
>> bjam" "-
>> sBOOST_BUILD_PATH=/var/scratch/boost:/var/scratch/boost/tools_bb" "-
>> sBOOST_ROOT=/var/scratch/boost/boost" "--boost=/var/scratch/boost/
>> boost" "--boost-build=/var/scratch/boost/tools_bb" "--debug-
>> configuration"  -l300 intel-10.0 -d2 preserve-test-targets=off -- 
>> dump-
>> tests -j8 link=static "--build-dir=/var/scratch/boost/results" >>"/
>> var/scratch/boost/results/bjam.log" 2>&1)...
>> # Running Boost.Build tests
>> Traceback (most recent call last):
>>    File "run.py", line 60, in <module>
>>      runner(root)
>>    File "/var/scratch/boost/tools_regression_src/regression.py", line
>> 193, in __init__
>>      self.main()
>>    File "/var/scratch/boost/tools_regression_src/regression.py", line
>> 551, in main
>>      getattr(self,action_m)()
>>    File "/var/scratch/boost/tools_regression_src/regression.py", line
>> 516, in command_regression
>>      self.command_test()
>>    File "/var/scratch/boost/tools_regression_src/regression.py", line
>> 317, in command_test
>>      self.command_test_boost_build()
>>    File "/var/scratch/boost/tools_regression_src/regression.py", line
>> 354, in command_test_boost_build
>>      "boost/bin.v2/libs/any/test/any_test.test"));
>> OSError: [Errno 2] No such file or directory: '/var/scratch/boost/
>> results/boost/bin.v2/libs/any/test/any_test.test'
>>
>> We get the exact same error message on all Sandia testers, and from
>> the looks of it, most other testers are having the same problem.  Any
>> help in getting testing going again would be appreciated.
>
> This is actually Boost.Build tests failing, but it could only happen
> if something in Boost.Any failed as well. Unfortunately, I don't see
> any suspicious changes in Boost.Any, Boost.Build, or regression  
> scripts.

Perhaps this is the source of the problem?

error: Unable to find file or target named
error:     'test_bitset.cpp'
error: referred from project at
error:     '../libs/serialization/test'

> Can you send me your bjam.log?

I can if you still need it, but it will take a while to regenerate  
the output.

-- Noel