Re: [boost] [EXTERNAL][testing][regression][spirit][geometry] What are the things that we HAVE TO fix before shipping 1.56.0?

Subject: Re: [boost] [EXTERNAL][testing][regression][spirit][geometry] What are the things that we HAVE TO fix before shipping 1.56.0?
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2014-07-31 00:36:50

On Jul 30, 2014, at 5:14 PM, Adam Wulkiewicz <adam.wulkiewicz_at_[hidden]> wrote:

> Barend Gehrels wrote:
>> Op 30 jul. 2014 om 20:08 heeft "Belcourt, Kenneth" <kbelco_at_[hidden]> het volgende geschreven:
>> 
>>> On Jul 30, 2014, at 4:51 AM, Adam Wulkiewicz <adam.wulkiewicz_at_[hidden]> wrote:
>>> 
>>>> Kenneth Belcourt wrote:
>>>>> On Jul 28, 2014, at 5:36 PM, Adam Wulkiewicz <adam.wulkiewicz_at_[hidden]> wrote:
>>>>> 
>>>>>> It's not a showstopper but the regression results still aren't displayed for Geometry master (after the addition of sublibs file): http://www.boost.org/development/tests/master/developer/geometry.html
>>>>>> We can see the results for develop and run tests locally but we can't do as extensive testing as it's done by the volunteers.
>>>>>> 
>>>>>> We wrote about it on Boost and Boost-Testing lists more than a month ago but nobody answered.
>>>>>> We also tried to contact one of the runners to re-run some tests, it didn't help.
>>>>>> With the tests missing I can't fully answer your question.
>>>>> I just made a change to see if I can get Geometry on master to work.  With luck, our testers should post results in a bit.
>>>> Some of the testers rerun the tests already but the situation stays the same.
>>>> Or should we wait for all of the testers to see the result of your changes?
>>> The changes I made were just to our local testers.  Frankly, I have no idea why geometry doesn’t show up in master, I’ll try to debug this a bit more this evening.
>>> 
>>> 
>> 
>> Thanks.
>> 
>> For Boost.Spirit it seems to be the same. No results on master, but on certain platforms (those of j.c. bell), there are results (July 25). The same as Geometry.
> 
> Interesting, in this case sublibs file was added 4 years ago. So either nobody noticed that tests are missing for 4 years or something else causes the problem. Assuming that it wasn't merged in master recently, or was it?
> 
> AFAIR there was some change in Config(?) made some time ago which also caused some problems with missing tests, e.g. in Geometry and Math. But this should be fixed now, it works in develop. May it be somehow related?
> 
> When I run:
> b2 --dump-tests status/
> the tests are listed. And AFAIR the results are sent to the server with logs and everything.
> 
> So I'm guessing that it's something wrong on the server-side or it's a bug in the Regression, assuming that the scripts/program generating the HTML results from XMLs sent by the runners is in this module.
> Should I create a ticket or do you have some other ideas?

The tests are in the tester composite xml file (e.g. Sandia-gcc-4.8.2.xml) so they’re getting built and trying to run.  Why they don’t show up in html could be that test-type and test-program in the xml test-log are both blank.

<test-log library="geometry/test" test-name="access" test-type="" test-program="" target-directory="boost/bin.v2/libs/geometry/test/core/access.test/gcc-4.8.2/debug" toolset="gcc-4.8.2" show-run-output="true”>

So I went back and looked in the test results/bjam.log and found this:

testing.capture-output /scratch/boost_testing/results/boost/bin.v2/libs/geometry/test/core/access.test/gcc-4.8.2/debug/access.run

    LD_LIBRARY_PATH="/sierra/sntools/SDK/compilers/gcc/4.8.2-RHEL6/bin:/sierra/sntools/SDK/compilers/gcc/4.8.2-RHEL6/lib:/sierra/sntools/SDK/compilers/gcc/4.8.2-RHEL6/lib32:/sierra/sntools/SDK/compilers/gcc/4.8.2-RHEL6/lib64:$LD_LIBRARY_PATH"
export LD_LIBRARY_PATH

    status=0
    if test $status -ne 0 ; then
        echo Skipping test execution due to testing.execute=off
        exit 0
    fi

Why is testing.execute is off?

Can you in master turn off all tests in geometry/test except for, say, core.  And perhaps all tests in core/Jamfile.v2 except for the access test and let tests cycle to see if that one test will run?  Maybe b2’s memory is getting thrashed?

— Noel