From: David Abrahams (dave_at_[hidden])
Date: 2003-11-15 10:47:32
Aleksey Gurtovoy <agurtovoy_at_[hidden]> writes:
> David Abrahams wrote:
>> Aleksey Gurtovoy <agurtovoy_at_[hidden]> writes:
>> > David Abrahams wrote:
>> >> Misha Bergal <mbergal_at_[hidden]> writes:
>> >> > 2. The python test fail if run as a part of status/jamfile - runs fine
>> >> > if ran from libs/python/test (see log below)
>> >> Baffling.
>> > It's easy to reproduce - include Boost.Python into the status/jamfile, and
>> > you'll get what we are getting. We would appreciate if somebody with
>> > adequate amount of bjam knoweledge could look at this in more detail -
>> > apparently we don't have enough qualification to understand what's
>> > happenning there, and certainly not enough time to get ourselves to that
>> > level.
>> OK, this is now fixed.
> Thank you!
>> However, I'll have to get Boost.Python tests
>> to use the primitives in tools/build/v1/testing.jam for running tests
>> if you want process_jam_log to work on it.
> We do! The ultimate goal is to have a report which would provide us with
> complete status of all libraries, for all platforms the regressions are run
OK, now done. Everyone with Python configured will get Boost.Python
tests automatically as part of building in the status directory.
Making this work caused some rather massive changes to the build/test
system, so please let me know if anything is now broken. This is
especially true for Unix users. I am only now starting to test the
changes on Linux.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk