From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Stump To: gcc@gcc.gnu.org, geoffk@cygnus.com Subject: Re: new automated testing facility now operational Date: Thu, 30 Mar 2000 15:57:00 -0000 Message-id: <200003302357.PAA11988@kankakee.wrs.com> X-SW-Source: 2000-03/msg00825.html Way cool. Yeah, I've thought we've needed it for 5 years now. Next one will be a, after much testing of nominated changes across lots of targets, the code gets migrated to the next release branch. You want your code in the release, you have to pass the test, then, the _system_ puts it in. Code that fails testing, is automatically moved to a side branch to allow other code being put in to pass it up. The more junk that goes in, the more that is derailed to a side branch. If nice code goes in, the system pats you on the back by arranging for it to go into the release branch. Need a well tested snapshot, but don't want to be burned, use the release branch. Like helping others, cleap up the stuff on the side branch. Now, lots of us folks have spare disk and spare cycles. Might be nice if you pass dated cvs command lines to others that you otherwise believe will work, (since you have nice bandwidth into the server), and have them bash on them to increase coverage. I'm thinking about extending the automated stuff out, not doing any of this by hand. I know I have a complete target lab with about 56 boards in it (28 totally free at the moment), all with ethernet, APC power control for dejagnu and so on, across 9 major CPU families. Certainly I have to already support these whee beasties. And it benefits me if problems are found before I `get' to the software. Ah, in time. Anyway, talk and toughts are cheap. Your actions are awesome and much harder, thanks.