new automated testing facility now operational

[Geoff Keating]

> Date: Mon, 3 Apr 2000 00:59:26 +0200 (CEST)
> From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>

> > - The rate of change on the GCC tree is so high now that, since a
> >   build and check takes about two hours, there is no way to test each
> >   patch individually.
> 
> Is the mail going to the committer having triggered the current test run
> or to all addresses in the ChangeLog since the last successful build? (I
> guess the later would be preferrable.)

It goes to all the addresses in the ChangeLog since the last (not
necessarily successful) build.

> A new mailing list @gcc.gnu.org (with a web archive, of course), that is
> Cc:ed on these messages would be nice. Have you already talked to Jeff?

Jeff is working on it.

> Are you planning to make your scripts (publicly) available, so that we can
> set this up for a couple of further targets?

There's not much to them, but yes, I do plan to do that.

However, there's a limit to how many of these things you want running.
They place additional load on the CVS server, and it should be
possible to get reasonable coverage with only two or three targets.

The purpose of this wasn't to act as a substitute for people testing
their patches themselves; in fact, the hope is that people will be
shamed into testing better.

In the long run, I'd like to see a policy that all patches should be
tested on some small group of targets, and that any patch which breaks
one of these targets will be rejected or reverted until it is fixed
and tested properly.

> Now, once the tree is stable again, I'll have to commit some patch that
> breaks the tree, just to see your nice system in action. :-) (Just
> kidding, of course!)

Oh, it's not quite stable yet.

-- 
- Geoffrey Keating <geoffk@cygnus.com>