Boost logo

Boost Testing :

From: Martin Wille (mw8329_at_[hidden])
Date: 2007-03-28 08:14:42


David Abrahams wrote:
> on Wed Mar 28 2007, Martin Wille <mw8329-AT-yahoo.com.au> wrote:
>
>> David Abrahams wrote
>>> The following message is a courtesy copy of an article
>>> that has been posted to gmane.comp.lib.boost.testing as well.
>> CC-ing me for messages that get sent to boost-testing doesn't help.
>> Those messages get put into the INBOX together with spam. We're lucky I
>> spotted your messages between the junk.
>
> You mean, you don't read them where they appear on boost-testing anyway?

The messages get sent to me only once. I have a filter setup for stuff
that goes to the boost-testing mailing list. That filter puts messages
into my boost-testing folder. But the filter fails if someone posts to
gmane and CCs to me.

>> It's the again wrong Python binary that got used to run the test; this
>> is the log snippet for gcc-3.4.5/extract_test:
>>
>>
>> /bin/sh: line 6: 5777 Segmentation fault /usr/bin/python2.3
>> "../libs/python/test/list.py"
>> >"/boost/head-regression/results/boost/bin.v2/libs/python/test/list.test/gcc-3.4.5_linux/debug/list.output"
>> 2>&1
>
> :(
>
>> The system's Python got chosen instead of the installation configured in
>> test-config.jam:
>>
>> using gcc : 3.4.5_linux : /usr/local/gcc-3.4.5/bin/g++wrap
>> --limit-memory=600 --limit-cpu=1800 : <root>/usr/local/gcc-3.4.5
>> <debug-symbols>off ;
>> using python : 2.4 : /usr/local/python/2.4/gcc-3.4.4 : : : <toolset>gcc
>> <toolset-gcc:version>3.4.5_linux ;
>
> Can you please post your *entire* xxx-config.jam so I don't have to
> piece it together from the Trac ticket and your amendments on this
> list and worry that I got it wrong?

Please find my test-config.jam for Linux/x86 attached.

>> regression.py invokes bjam like:
>>
>> bjam toolset1 toolset2
>
> Yes, I know. Could you please post the actual bjam command-line
> issued by your invocation of the regression script?
>
> Failing that, could you post the command used to invoke regression.py
> (I really would prefer the bjam command-line if possible)?

I don't actually see the command anywhere. I use

I invoke regression.py this way:

/path/to/regression.py test --v2
--toolsets=gcc-3.2.3_linux,gcc-3.3.6_linux,gcc-3.4.5_linux,gcc-4.0.3_linux,gcc-4.1.0_linux,intel-9.0-linux

IIUC, this should result in:

/path/to/bjam --v2 -sBOOST_BUILD_PATH=$BOOST_BUILD_PATH
-sBOOST_ROOT=$BOOST_ROOT gcc-3.2.3_linux gcc-3.3.6_linux gcc-3.4.5_linux
gcc-4.0.3_linux gcc-4.1.0_linux intel-9.0-linux

$BOOST_BUILD_PATH points to a directory that contains only test-config.jam.

> I have hardware I can use. I could probably replicate your set-up, or
> at least, enough of it to see the problems you're experiencing

The key components to this problem (IMHO) are:

System's Python v 2.3 built with gcc 3.3.x
Test Python v 2.4 built with gcc 3.4.x

The system is a not very up-to-date Gentoo. (I avoided updates in order
not to disturb the tests; we really don't need more mess now.)

>> I'm on IRC in EFnet/#boost and in freenode/#boost (there's a relay
>> between those two, anyway). Unfortunately, I can't promise to be there
>> at any specific time.
>
> Care to tell me what your ID is so we don't have to bother the group?

_m_. I assume it was you who were asking for me a moment ago. I replied,
but apparently too late, since you quit right after my "yes".

Regards,
m

using gcc : build_tools : : ;

using python : 2.3 : /usr : : ;

using gcc : 3.2.3_linux : /usr/local/gcc-3.2.3/bin/g++wrap --limit-memory=600 --limit-cpu=1800 : <root>/usr/local/gcc-3.2.3 ;

using gcc : 3.3.6_linux : /usr/local/gcc-3.3.6/bin/g++wrap --limit-memory=600 --limit-cpu=1800 : <root>/usr/local/gcc-3.3.6 ;

using gcc : 3.4.5_linux : /usr/local/gcc-3.4.5/bin/g++wrap --limit-memory=600 --limit-cpu=1800 : <root>/usr/local/gcc-3.4.5 <debug-symbols>off ;
using python : 2.4 : /usr/local/python/2.4/gcc-3.4.4 : : : <toolset>gcc <toolset-gcc:version>3.4.5_linux ;

using gcc : 4.0.2_linux : /usr/local/gcc-4.0.2/bin/g++wrap --limit-memory=600 --limit-cpu=1800 : <compileflags>"-D_GLIBCXX_DEBUG=1" <root>/usr/local/gcc-4.0.2 <debug-symbols>off ;
using python : 2.4 : /usr/local/python/2.4/gcc-4.0.0 : : : <toolset>gcc <toolset-gcc:version>4.0.2_linux ;

using gcc : 4.0.3_linux : /usr/local/gcc-4.0.3/bin/g++wrap --limit-memory=600 --limit-cpu=1800 : <root>/usr/local/gcc-4.0.3 <debug-symbols>off ;
using python : 2.4 : /usr/local/python/2.4/gcc-4.0.0 : : : <toolset>gcc <toolset-gcc:version>4.0.3_linux ;

using gcc : 4.1.0_linux : /usr/local/gcc-4.1.0/bin/g++wrap --limit-memory=600 --limit-cpu=1800 : <root>/usr/local/gcc-4.1.0 <debug-symbols>off ;
using python : 2.4 : /usr/local/python/2.4/gcc-4.0.0 : : : <toolset>gcc <toolset-gcc:version>4.1.0_linux ;

using intel-linux : 9.0 : /opt/intel/cc/9.0/bin/icpc ;
Send instant messages to your online friends http://au.messenger.yahoo.com


Boost-testing list run by mbergal at meta-comm.com