hartmutkaiser@t-online.de (Hartmut Kaiser) writes:
Martin Wille wrote:
Anyhow, I think your point about multiple reporting is a good one. The volume of tests is just too high. Fewer, more comprehensive, tests would be easier to monitor.
This could be implemented by using another build target.
I'm under the impression that the test results aren't monitored by the library maintainers unless we're close to a release. So, it doesn't make much sense to run all the tests all the time.
What about generating an email to the maintainers of the corresponding library, which makes sure they will know about a failed test ... :-)
Yeah, great idea. That's what the BuildBot does. Only, it first sends mail to the person that broke the test, in hopes that (s)he'll fix the problem. That's much better, IMO. -- Dave Abrahams Boost Consulting www.boost-consulting.com