Boost Testing :
From: John Pavel (jrp_at_[hidden])
Date: 2007-11-07 11:54:48
Rene, Thanks. Perhaps one approach would be to get the test systems to generate data that required less post-processing.
And while we're on the subject, I note that some of my logs get chopped at 65535 chars. This is usually as a result of a lot of template expansion diagnostic. Unfortunately, since it is the first 65535 chars that are reported, the failure cause isn't visible for tests that fail. Ideally you would take the first 10000 chars and the last 55535 chars and merge then into a report with a "..." in between!
At the moment only failed tests result in accessible logs. However, it would be helpful for developers to be able to see warnings, etc, even in successful tests.
From: Rene Rivera <grafikrobot_at_[hidden]>
Sent: 07 November 2007 16:25
To: Running Boost regression tests <boost-testing_at_[hidden]>
Subject: Re: [Boost-testing] Frequency/timing of regression summary generation?
John Pavel wrote:
> Beman, thanks. The current (16:07) summary is from 02:41, which is
> some way off 3.5h, so I am still a bit mystified, Best, John
I'm suspecting some recent changes to the reports has made the interval
jump up significantly. Which is why I've been thinking of putting in
some log of the interval. And in case anyone is curious I suspect adding
the rev number to all the pages has caused things to slow down.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo _______________________________________________ Boost-Testing mailing list Boost-Testing_at_[hidden] http://lists.boost.org/mailman/listinfo.cgi/boost-testing