Re: [Boost-testing] How to debug a testing problem?

From: Beman Dawes (bdawes_at_[hidden])
Date: 2005-06-15 07:51:10

"Aleksey Gurtovoy" <agurtovoy_at_[hidden]> wrote in message 
news:m1k6kwzgx2.fsf_at_tulip.office.meta...
> Beman Dawes writes:
>...
>> and only on one simple test. Say config_info.
>
> Unless it's possible to specify this through bjam command line, I'm
> afraid this part is not that simple to achieve. Of course, what you
> can always do is to temporary comment out everything but config tests
> from "status/Jamfile".

>From the bjam command line, you would just say:

   bjam ... config_info

That will cause only the config_info target to be run.

The problem with regression.py --bjam-options is that it doesn't place them 
last on the bjam command line. For example:

   python regression.py test ... --bjam-options=config_info

produced:

   bjam.exe ... config_info "-sALL_LOCATE_TARGET=D:\boost-auto-regr\results"

That doesn't work because config_info has to be the last command line entry 
(not counting the 1>> and 2>&1 redirection).

Is that something that is easy to change?

--Beman