Re: [Boost-build] Broken V2 testing.

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-10-24 01:33:16

Rene Rivera wrote:

> I've been trying to run the unit tests for BBv2, after fixing the
> MinGW/MSYS problem. And as it stands, running these tests is pointless
> for me. With reported failures like this:
> 
> ====
> FAILED
> path_features             :  File x/bin/gcc/debug/m.exe not added as
> expected
> -------- all changes caused by last build command ----------
> Added files   : ['x/bin/gcc-mingw_special-3.4.5/debug/m.exe',
> 'x/bin/gcc-mingw_special-3.4.5/debug/m.o']
> Removed files : []
> Modified files: []
> Touched files : []
> ====
> 
> It makes it useless for anything but the bare install and setup. Which
> as far as I can think no one would have. How hard is it to make the test
> system flexible enough to make the above pass? Or to put it another
> way... Please fix this!

Rene, as I've said in an email some time ago you need to use

   python test_all.py gcc-mingw_specific-3.4.5 

I think it's not very hard to specify by hand, and on the other hand it's
pretty hard to make the Python-based test system figure out which toolset
is defined first in your user-config.jam.

- Volodya