On Wed, Oct 6, 2010 at 3:16 PM, Wes Hardaker <[email protected]
> wrote:
> >>>>> On Wed, 6 Oct 2010 09:07:56 +0100, Dave Shield <
> [email protected]> said:
>
> DS> - We were talking about having some form of (optional)
> DS> automatic build report emailed to us, so that we could
> DS> get some feel for how widely tested things had been.
> DS> Did anything ever come of this?
>
> No, not yet. And it's to late to start on it for 5.6, unfortunately.
>
The Valgrind nightly build infrastructure might be a good start. There is a
script nightly/bin/nightly in the Valgrind repository that does the
following:
* Determine the revision number that corresponds to the most recent
modification that is at least 24h old (r1).
* Query the most recent revision number (r2).
* If r1 == r2, stop.
* Run the regression tests for revision r1.
* Run the regression tests for revision r2.
* E-mail the diffs between the output of the previous two steps to the
developer/coder mailing list.
Sending diffs out in addition to the actual regression test output makes it
very easy to spot whether behavior changes have been introduced.
See also nightly/README.txt in the Valgrind Subversion repository (svn://
svn.valgrind.org/valgrind/trunk) for more information.
Bart.
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
