|
Boost Testing : |
Subject: Re: [Boost-testing] errors (wrong URLs) in test report matrix
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2018-03-11 23:35:06
On 11.03.2018 19:23, Steven Watanabe via Boost-Testing wrote:
> AMDG
>
> On 03/11/2018 05:08 PM, Stefan Seefeld via Boost-Testing wrote:
>> I'm sorry if this mail is sent to the wrong place - I'm not entirely
>> sure where to report issues with the test report generation on the
>> boost.org website.
>>
>> I'm observing a bug in the test report matrix, where a test failure
>> report links to the wrong output page:
>>
>> Specifically, I'm looking at
>> http://www.boost.org/development/tests/develop/developer/output/teeks99-09-b-win2016-64on64-boost-bin-v2-libs-python-test-builtin_converters-test-msvc-9-0-dbg-adrs-mdl-64-thrd-mlt.html,
>> which reports a failure in a `builtin_converters` test. The only
>> "content" under the title is a reference to another page:
>> http://www.boost.org/development/tests/develop/output/teeks99-09-b-win2016-64on64-boost-bin-v2-libs-python-test-msvc-9-0-dbg-adrs-mdl-64-thrd-mlt.html,
>> which contains output of two commands ("compile" and "link"), but to a
>> different test: `map_indexing_suite`.
>>
>> Needless to say, `builtin_converters` and `map_indexing_suite` have
>> nothing to do with each other.
>>
> The problem seems to be that they both get written to the same file.
>
>> What logic does generate the test report, and where should I report this
>> bug ?
>>
> The repository is here:
> https://github.com/boostorg/regression/
> I suspect the problem is in process_jam_log, but
> I'd need to check the XML file to be sure.
[Here is an idea for a GSoC project: improve the test report generation,
to fix bugs, and just improve the GUI to make the huge set of tests more
easy to navigate.]
Stefan
-- ...ich hab' noch einen Koffer in Berlin...