Boost logo

Boost Testing :

From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-11-08 01:08:29

Just FYIs...

Aleksey Gurtovoy wrote:
> Report generation times are greatly affected by:
> 1) the overall number of failing test cases (an output page is generated
> for each of these).

Which step in the process are those generated?

> 2) the number of updated toolsets since the last report generation cycle
> (some of the intermediate report data is cached).

I've seen this one go up to 10 toolsets at a time.

> 3) used version of xsltproc/libxml/libxslt.

xsltproc: 1.1.21
libxml: libxml2 2.6.30
libxslt: 1.1.21

> -- not to mention general factors such as processor load.

Report generation is all this machine does currently. But what seems to
be taking most of the CPU time is:

Writing document summary_.html
# Making summary user report...
# xsltproc -o
--param run_date "'2007-11-08T02:33:52Z'" --param explicit_markup_file
  --param source "'trunk'" --param mode "'user'"
Writing document summary_.html

It's up to 80 CPU minutes just on that, and onwards.

-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. -
-- rrivera/ - grafik/
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

Boost-testing list run by mbergal at