Boost.Build and Boost.Python testing

From: Misha Bergal (mbergal_at_[hidden])
Date: 2004-02-25 03:32:03

Sorry if I am posting to the wrong forum. 

For some time we (and other regression testers) had "missing" test
results for some failing Boost.Python tests. The investigation showed
that the problem probably lies in interaction of process_jam_log and
Boost.Build python testing subsystem. Here is the bjam output to be
processed by the process_jam_log:

boost-test(RUN_PYD) "injected" : "libs\python\test\injected.py" "libs\python\test\injected.cpp"

MkDir1 C:\Users\Misha\Stuff\boost_regression\main\results\bin\boost\libs\python\test\injected.test

mkdir "C:\Users\Misha\Stuff\boost_regression\main\results\bin\boost\libs\python\test\injected.test" 

MkDir1 C:\Users\Misha\Stuff\boost_regression\main\results\bin\boost\libs\python\test\injected.test\borland-5.5.1

mkdir "C:\Users\Misha\Stuff\boost_regression\main\results\bin\boost\libs\python\test\injected.test\borland-5.5.1" 

MkDir1 C:\Users\Misha\Stuff\boost_regression\main\results\bin\boost\libs\python\test\injected.test\borland-5.5.1\debug

mkdir "C:\Users\Misha\Stuff\boost_regression\main\results\bin\boost\libs\python\test\injected.test\borland-5.5.1\debug" 

...skipped <@boost!libs!python!test\injected.test\borland-5.5.1\debug>injected.run for lack of <@boost!libs!python!test\injected.pyd\borland-5.5.1\debug>injected.pyd...

...failed updating 105 targets...
...skipped 295 targets...
...updated 420 targets...

The interesting line here is:

...skipped <@boost!libs!python!test\injected.test\borland-5.5.1\debug>injected.run for lack of <@boost!libs!python!test\injected.pyd\borland-5.5.1\debug>injected.pyd...

process_jam_log parses this line to get target directory (path before
"for lack of") and library directory (path after "for lack of"). 

If these directories are different process_jam_log recognizes this
line as a library dependency and proceed to build <lib result="fail">
part of xml report file.

In these case the directories are the same, which is incorrect? and
strange because injected.pyd is created in
<@boost!libs!python!test\injected_ext.pyd\borland-5.5.1\debug> for
not-failing compilers.

Unfortunately I don't have enough knowledge of Boost.Build to see what
is going on there. Any help will be appreciated.

-- 
Misha Bergal
MetaCommunications Engineering