[boost] [build][geometry][regression] Geometry develop regression tests are blank

Subject: [boost] [build][geometry][regression] Geometry develop regression tests are blank
From: Adam Wulkiewicz (adam.wulkiewicz_at_[hidden])
Date: 2017-03-29 12:10:52

Hi,

Boost.Geometry develop tests 
(http://www.boost.org/development/tests/develop/developer/geometry.html) 
stopped showing around 22.03. The first blank run 
(teeks99-03-dc3.9-1z-Docker-64on64) is from Wed, 22 Mar 2017 01:20:13. 
Do you have an idea what may be the cause? I see that many changes in 
Build and Regression was done around 22.03. Geometry was also modified 
that day but the first commit is from 12:40+1 so later than the first 
blank run.

I checked the XML of one of them (teeks99-09-n-win2012R2-64on64) and it 
seems that the revision attribute of <test-log> tag is not set for the 
most of the tests.

I'm currently running the regression.py myself in hope of finding the 
cause. I see that in bjam.log the only tests that are dumped are:

boost-test(RUN_PYD) "geometry/__boost_check_library__" : 
"status/boost_check_library.py"
boost-test(RUN_PYD) "geometry/extensions/__boost_check_library__" : 
"status/boost_check_library.py"
boost-test(RUN) "geometry/index/varray_old" : 
"libs/geometry/index/test/varray_old.cpp"
boost-test(RUN) "geometry/index/varray" : 
"libs/geometry/index/test/varray.cpp"
boost-test(RUN_PYD) "geometry/index/__boost_check_library__" : 
"status/boost_check_library.py"

varray tests are the only ones that are run at the most top level of 
Geometry Jamfiles (of sublib geometry/index in this case) with test-suite:
https://github.com/boostorg/geometry/blob/develop/index/test/Jamfile.v2#L24
The rest of the tests is run with build-project, also for the main part 
of the library:
https://github.com/boostorg/geometry/blob/develop/test/Jamfile.v2#L26

The varray tests results are shown on the regression page and can be 
found in bjam.log and in XML file with revision set.
The rest of the tests is neither dumped nor has the revision set, 
however they are run during regression testing so can be found in 
bjam.log and also in XML file but with empty revision.

Adam