|
|
Boost Testing : |
Subject: Re: [Boost-testing] [urgent] Testing help needed..
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2014-01-03 14:36:56
AMDG
On 01/03/2014 10:22 AM, Daniel James wrote:
> On 3 January 2014 18:22, Steven Watanabe <watanabesj_at_[hidden]> wrote:
>> AMDG
>>
>> On 01/03/2014 07:27 AM, Rene Rivera wrote:
>>> On Fri, Jan 3, 2014 at 9:20 AM, Beman Dawes <bdawes_at_[hidden]> wrote:
>>>
>>>>
>>>> One visual problem is that the full SHA is so wide that it messes up the
>>>> width of the table columns. Cutting the SHA down to the first 6 or 8
>>>> characters should be sufficient for reporting purposes.
>>>>
>>>> Rene, could you do that?
>>>>
>>>
>>> I could.. But would it not be better to do that in the report generation..
>>> As it would be useful to have the full SHA in the raw data for generating
>>> links to github commits (for example).
>>>
>>
>> +1. This is handled at common.cpp:480
>> in insert_runners_rows.
>
> Is the xsl dead? Should we delete it?
>
The scripts can still use the xsl
as a fallback if the boost_report
executable isn't present. The
behavior should be equivalent, right
now (except for performance). I
left the xsl scripts around in case
anything went wrong. At this point,
I'd say they can be deleted, especially
if we're going to be making any changes.
In Christ,
Steven Watanabe