Re: [Boost-testing] [boost] What's up with the trunk test summary?

Subject: Re: [Boost-testing] [boost] What's up with the trunk test summary?
From: K. Noel Belcourt (kbelco_at_[hidden])
Date: 2008-09-07 17:43:57

Hi Rene,

On Sep 7, 2008, at 3:29 PM, Rene Rivera wrote:

> K. Noel Belcourt wrote:
>>
>> On Sep 7, 2008, at 2:12 PM, Rene Rivera wrote:
>>
> OK, the html files should be generated to results-root/trunk/all/*.  
> The
> build_results.sh doesn't directly generate any html. The work is done
> with the python script and the xslt transformations. And at minimum
> there are files missing from the ZIP that I get when the results are
> generated. For example I have a "$/trunk/all/developer/toc.html" which
> corresponds to the left side navigation which is missing from the ZIP.

[ snipped lots of good info. ]  Thanks, that helps.

I found a quad quad core system with a newer xsltproc and ran the  
report generation on that system.  It seems to have worked and the  
developer trunk pages look reasonable.

I think this was the phase that was failing,

#     Making detailed developer  report...

but everything looks much better now.  I'll get a cron job setup and  
probably run the report generation an hour after the previous run  
completes (a complete run takes about 30 minutes).

Trunk reporting is back!!

Thanks again for all the help Rene.

-- Noel

Here's the xsltproc version info that seems to work.

Using libxml 20626, libxslt 10117 and libexslt 813
xsltproc was compiled against libxml 20626, libxslt 10117 and  
libexslt 813
libxslt 10117 was compiled against libxml 20626
libexslt 813 was compiled against libxml 20626