From: Beman Dawes (bdawes_at_[hidden])
Date: 2003-12-03 13:58:44
At 11:57 AM 12/3/2003, Misha Bergal wrote:
>Beman Dawes <bdawes_at_[hidden]> writes:
>> At 11:41 AM 12/1/2003, Misha Bergal wrote:
>> >The process_jam_log doesn't distinguish between the tests with the
>> >same name but different libs (for example, "list" test is in the mpl
>> >and python libs) and assigns all "list" test results to
>> >"conf. problem" is probably wrong, but in any case if root of the
>> >problem is fixed then it is going to go away. The same is with
>> >"missing" test results in Boost.Python.
>> This is supposed to be working properly now. If you are still having
>> problems, let me know.
>process_jam_log hangs on our bjam_log. I can send our bjam.log if it
>is going to help.
Please do. Also any other information to help debug the problem.
Does it only hang on large runs? Will it still hang if you run just one
test? One toolset?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk