Boost Testing :
From: Beman Dawes (bdawes_at_[hidden])
Date: 2007-10-16 09:54:51
Beman Dawes wrote:
> Jeff Garland wrote:
>> Beman Dawes wrote:
>>>>> At some point my Linux machine will also start doing a set of release
>>>>> tests. I've changed my cycle to: trunk test gcc-4.2.2, trunk regression
>>>>> results, release test gcc-4.2.2, trunk regression results. This should
>>>>> increase the response of the trunk regression results.
>>>> Good. I'm just now trying to figure out how to run the release
>>>> regression results. I'll start by trying the test procedure Aleksey
>>>> posted earlier today.
>>> OK, tests work.
>> So are they being posted somewhere? Can we put a link on the main page?
> Those are just tests of the xml reporting process, run as a confidence
> test to verify I can run xml report generation and get the expected results.
> I'm working on the real release branch reports right now.
I'm generating the reports, but they are empty. This on Ubuntu Linux, by
Downloading the .zip files from the ftp site seems to be working OK, but
after the run the "merged" directory is empty. Presumably that's the
source of the report content, so it isn't unexpected that the reports
themselves are empty. The "processed" directory has the .xml files for
the two current runners, so I'm guessing the process is working up to
the point of the merge.
It would help me if you would run the release branch reports once on
your machine, and then send me the script you used, the starting
directory structure you ran it in, and tell me the point in the
directory structure you ran the script from.