Adam Wulkiewicz wrote:
Hi,
I noticed that for the latest runs the tests of Geometry are missing. Surprisingly not all, 2 tests for geometry/index sublib are present.
Initially I thought that it may be caused by the recent modularization but I didn't noticed any problems in any of the libraries I checked randomly. <snip> Now I see problems in other libraries too. So I decided to try running the tests by myself. I tried: 1. Windows + GitBash -> a lot of "can't find xxx file" errors (b2 headers didn't work properly) 2. Windows + GitBash with admin rights -> exactly what can be seen in the tests, bjam.log shows that only 2 tests from Geometry was choosen for testing 3. Windows + cmd with admin rights -> everything is ok (in case you wanted to check it - runner Test2) 4. Linux -> also everything is ok (runner Test) 3 and 4 was ok because there was only 1 module tested --libraries=geometry. For 2 I tested also core and test.
I tested it locally running (in case someone would like to play with it too): b2 status --dump-tests --debug-configuration and found out that the problem is related with the usage of 'build-project' in Jamfiles. This is not only seen in Geometry, though it's the library that uses this instruction most extensively. E.g. see: http://www.boost.org/development/tests/develop/developer/geometry.html http://www.boost.org/development/tests/develop/developer/math.html http://www.boost.org/development/tests/develop/developer/functional-hash.htm... The projects aren't parsed recursively since ~6.06.2014. What's going on? May it be caused by some invalid Jamfiles added recently for some other libraries? Regards, Adam