|
Boost Testing : |
From: David Abrahams (dave_at_[hidden])
Date: 2006-07-17 08:08:21
"Sean Huang" <huangsean_at_[hidden]> writes:
>> http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/output/Huang-WinXP-x64-boost-bin-v2-libs-python-test-exec-test-msvc-8-0-debug-threading-multi_release.html
>>
>> seems to indicate that it's failing to find the PythonXX.dll (where
>> XX is your python version) in g:\Tools\python\libs. It's either a
>> tester configuration error, or an error in the BBv2 python toolset
>> file. This should be easy for the tester to diagnose, but there's
>> not much I can do without more information. Can you look into it,
>> Sean?
>>
> Dave,
>
> I took a closer look at the problem and it is because the python version
> installed on the test machine is for win64-x64 (AMD64). That explains why
> all win32 versions failed but win64 versions worked. I tried to install
> win32-python side-by-side but it would not allow me (if I uninstall the
> 64-bit version and install the 32-bit version then I guess the 64-bit
> versions will fail). Looks like we cannot test both 32-bit and 64-bit of
> python library on the same machine.
Not without VMWare, I guess ;-)
> I can change the toolset name to
> something other than msvc-8.0 so it can be marked as expected failures. But
> the more important issue is that the current toolset naming convention
> probably should include platform also.
Maybe so.
-- Dave Abrahams Boost Consulting www.boost-consulting.com