|
Boost : |
From: Beman Dawes (bdawes_at_[hidden])
Date: 2007-10-04 17:36:56
As an experiment, I've got a script that is checking svn every 15
minutes, and if there is a change, running the regression tests and
uploading results to a web site.
For current VC++ results, see
http://mysite.verizon.net/beman/win32-trunk-results.html
On these runs the reporting is set to show a row only if the results are
something other than a simple "pass" without link.
For slightly outdated Linux results, see
http://mysite.verizon.net/beman/ubuntu-trunk-results.html
Here the results show all tests, regardless of result.
The idea is to supplement the regular regression tests at
http://beta.boost.org/development/tests/trunk/developer/serialization.html
with rapid turnaround tests on a few major platforms, aimed at giving
developers quick response as they try to fix bugs affecting platforms
they don't have access to. At the current level failures, the Win32
tests are turning around in 11 minutes while the Linux tests turn in 4
minutes. Thus worst case developers can see test results in 26 minutes!
It seems to me this might be helpful to developers. Opinions?
Presumably in regular use the upload would go to a centralized site. Or
maybe decentralization is useful for reliability; a boost web page could
contain links. Opinions on that?
Which reporting do you prefer? My preference is just to show the tests
with something to report.
--Beman
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk