Re: [jamboost] testing.jam - weird behavior? (Re: 1.30.2 ready for release?)

From: Beman Dawes (bdawes_at_[hidden])
Date: 2003-08-17 12:39:19

At 07:53 AM 8/17/2003, Aleksey Gurtovoy wrote:
>[bjam.log]
>...
>boost-test(COMPILE_FAIL) "static_assert_test_fail_8" :
>"libs\libs\static_assert\static_assert_test_fail_8.cpp"
>boost-test(COMPILE_FAIL) "static_assert_test_fail_7" :
>"libs\libs\static_assert\static_assert_test_fail_7.cpp"
> ^^^^^^^^^
>
>This, in turn, leads to erroneous detection of the library name further 
in
>the tools chain, and ultimately to incorrect summary and detailed
>regression
>reports - http://tinyurl.com/jtpd (the yellow cells in the middle).
>
>The old revision works exactly as wanted (however weird it is):
>
>boost-test(COMPILE_FAIL) "static_assert_test_fail_8" :
>"libs\static_assert\static_assert_test_fail_8.cpp"
>boost-test(COMPILE_FAIL) "static_assert_test_fail_7" :
>"libs\static_assert\static_assert_test_fail_7.cpp"
>
>
>I would appreciate if someone with bjam expertise explained what's
>happening here and what would be the right fix.

Aleksey,

This bit me about two weeks ago, and I added a workaround to 
process_jam_log.cpp. I just checked CVS, at it did get checked in at that 
time. If you're still having trouble even with that fix, let me know.

--Beman