Boost Testing :
From: David Abrahams (dave_at_[hidden])
Date: 2005-06-02 11:21:30
Aleksey Gurtovoy <agurtovoy_at_[hidden]> writes:
> Douglas Gregor writes:
>>> * Then I would use a real regression logs and commenting out parts of
>>> XSLT code to find out what the bottlenecks are.
>> After some poking around, I found this little resource leech:
>> - <xsl:key
>> - name="a"
>> - match="."
>> - use="concat( @library, '@', @test-name )"/>
>> It was probably just some experimental code dropped in at one point,
>> but yanking this out turned a 70-second xsltproc run into a 6-second
>> run. The full issues.html generation takes 5-10 minutes now, instead
>> of 90.
> Oh, wonderful. Ideally, we'd like to keep it under 5, but for now this
> is good enough.
>>> Don't hesitate to ask more questions - we very much appreciate you
>>> looking into this.
>> And I appreciate the help!
>> I've committed some changes to the XSLT and a little tweak to
>> boost_wide_reports.py. The issues page should build much faster now
>> and I've worked out most (not all!) of the kinks. If all goes well on
>> your end, could you re-enable issue page generation?
Pretty nice. Here's the thing: compared to my original suggestion,
it's a bit hard for me to see if any of my libraries are failing.
One other point: when I click through any of the failures, I get "page
-- Dave Abrahams Boost Consulting www.boost-consulting.com