Boost Testing :
Subject: Re: [Boost-testing] Boost.Build tests failing
From: Maxime van Noppen (maxime_at_[hidden])
Date: 2011-01-21 10:00:33
On 01/21/2011 03:27 PM, Vladimir Prus wrote:
> What parts of this paths exists?
Only 'results'. There's nothing else than a results/bjam.log that I
didn't see before (duh!) and which contains a valuable logfile. I
somehow got caught by a problem that occurred before and that I posted
to this list before : the command line set in the crontab is :
> python2 run.py --runner='maxime.altribe.com-gcc' --toolsets=gcc-4.5.1 --bjam-options='-j4' --tag='branches/release'
Though g++ was upgraded to g++ 4.5.2 (didn't notice it till now in fact)
and so the script fails as it doesn't find g++-4.5.1 anymore I presume.
Can I just skip the --toolsets argument or at least use something more
generic so I don't get this error again?
Running the tests with --toolset=gcc-4.5.2 seems to work (it's running