>>>>> "Mark" == Mark Wielaard <[EMAIL PROTECTED]> writes:
Mark> I hope that I can cleanup Mauve enough before next week (when we Mark> will create the 0.07 snapshot release) to activate a autobuilder Mark> which we can use to track failures. But Currently Mauve is still Mark> to fragile for this. FWIW, I run Mauve as part of my nightly builds. I don't think Mauve is all that fragile, it hardly ever seems to be the part of the process that has trouble. These days the nightly tester is doing quite a bit: * Build gcc from scratch. Run the test suite including Mauve and Jacks * Build classpath from scratch with new gcj and jikes * Build rhug with new gcj * Build GNU Crypto and Kawa with gcj * Run Classpath/libgcj comparison and JAPI comparison Also I run the test suites for all of these things. Some of it doesn't work that reliably... rhug hasn't built completely in months, classpath fails with gcj. Of course, I wouldn't know that without the nightly tester :-) I'm not publishing the info anywhere, I just have it send me email. And the scripts to do all this are a little ugly. Still, as long as the builds are done when I start work in the morning, I'm happy to add stuff... ideally I'd have a recipe (so I don't have to think :-). I'd be happy to send the reports somewhere, too, if there were agreement on where. Tom _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
