|
Boost Testing : |
From: Beman Dawes (bdawes_at_[hidden])
Date: 2007-09-18 22:21:57
Beman Dawes wrote:
> Sebastian Redl wrote:
>> Beman Dawes wrote:
>>> The "very small addition" is to display the revision number, in the
>>> form "rev 12345" or similar, in the column header, centered under the
>>> "runner". The number will be supplied as the value for a new
>>> "revision" property in the results file. Here is the python code that
>>> will create it, to give you the context:
>>>
>>> results_xml.startElement(
>>> 'test-run'
>>> , {
>>> 'tag': tag
>>> , 'platform': platform
>>> , 'runner': runner_id
>>> , 'timestamp': timestamp
>>> , 'source': source
>>> , 'run-type': run_type
>>> , 'revision': revision
>>> }
>>> )
>> Hi,
>>
>> That's a pretty trivial change, but I'd need some data to actually test
>> it. Where do I get regression XML from, and how do I run the
>> transformations with all paths correct?
>>
>> Attached is how I would imagine this to work (as a patch against the
>> current trunk).
>
> Wow! Thanks! That is a huge help!
>
> I've just finished some initial testing here on the runner script
> changes to generate 'revision' and will try them live on the
> 'BGD-Ubuntu' runner in two or three hours.
The BGD-Ubuntu.xml file just uploaded did contain revision="39377", so
if Rene could test against Sebastian's proposed patch I'd appreciate it.
I'll wait until tomorrow morning to commit the script changes, and then
will watch all day for any reports of problems.
--Beman