[Boost-build] Buggy clean.py test in the latest nightly build (31.03.2007.).

From: Jurko Gospodnetiæ (jurko_for_boost_at_[hidden])
Date: 2007-04-01 06:46:20

   Hi.

   I do not yet fully understand how the boost build unit tests work but 
it seems to me that the clean.py test, and possibly more of the whole 
unit testing framework used, is broken in several ways:

   Using nightly builds from 22.03.2007. and 31.03.2007.:

   1. When run with a msvc toolset expects its targets under the 
/bin/msvc/debug folder and the results are placed under the 
/bin/msvc/debug/threading-multi folder.

   2. Tests the '--clean' parameter twice instead of testing '--clean' 
and '--clean-all'.

   3. Tests pass even if I change random expect_removal() tests to 
expect_nothing() and vice-versa. This happens even if I change the file 
folder to 'bin/$toolset/debug/threading-multi' instead of 
'bin/$toolset/debug'.

   Using the milestone 11 release:

   1. msvc toolset places its targets in the bin/msvc/debug folder by 
default as expected by the tests.

   2. --clean rule was tested twice instead of testing --clean-all in 
this release as well.

   3. Changing expect_removal() and expect_nothing() tests fails those 
tests as expected.

   4. Changing file paths used in the tests is correctly detected as a 
test failure.

   Hope this helps...

   Best regards,
     Jurko Gospodnetiæ