From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 734 invoked by alias); 15 Apr 2002 18:27:14 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 727 invoked from network); 15 Apr 2002 18:27:13 -0000 Received: from unknown (HELO Cantor.suse.de) (213.95.15.193) by sources.redhat.com with SMTP; 15 Apr 2002 18:27:13 -0000 Received: from Hermes.suse.de (Charybdis.suse.de [213.95.15.201]) by Cantor.suse.de (Postfix) with ESMTP id 584F41E8BA; Mon, 15 Apr 2002 20:27:13 +0200 (MEST) Received: from aj by arthur.inka.de with local (Exim 3.34 #1) id 16xB0L-0002b6-00; Mon, 15 Apr 2002 20:15:05 +0200 Mail-Copies-To: never To: Geoff Keating Cc: jason@redhat.com, mark@codesourcery.com, gcc@gcc.gnu.org Subject: Re: GCC 3.1 Release References: <46690000.1018660657@gandalf.codesourcery.com> <87662vicoi.fsf@creche.redhat.com> <200204151750.g3FHoqE12780@desire.geoffk.org> From: Andreas Jaeger Date: Mon, 15 Apr 2002 11:36:00 -0000 In-Reply-To: <200204151750.g3FHoqE12780@desire.geoffk.org> (Geoff Keating's message of "Mon, 15 Apr 2002 10:50:52 -0700") Message-ID: User-Agent: Gnus/5.090006 (Oort Gnus v0.06) XEmacs/21.4 (Artificial Intelligence, i386-suse-linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-04/txt/msg00616.txt.bz2 Geoff Keating writes: >> Cc: Mark Mitchell , gcc@gcc.gnu.org >> From: Jason Merrill >> Date: Sun, 14 Apr 2002 14:05:55 +0100 >> User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.1 (i686-pc-linux-gnu) >> >> >>>>> "Tom" == Tom Tromey writes: >> >> > What I'd like to see in the future is for people to set up automated >> > regression testers, say like Geoff's, that test these platforms. Then >> > we simply won't introduce problems in the first place. >> >> > In fact what I'd really like to see is a requirement for such a >> > regression tester for every platform that is considered release >> > critical. (I'm sure the logistics of this are difficult.) >> >> Absolutely. Geoff, how hard would it be for someone on the net to set up a >> slave tester to improve coverage? I'd like to keep the bookkeeping >> centralized, but the actual testing work can and should be distributed. > > Once sufficiently fast hardware is available, setting up a slave > tester should be very easy. I think it should go like this: > > 1. Set up a tester with some reasonably reproducible software > configuration (so that others can reproduce bugs). For example, > the current tester is configured as "Red Hat Linux 7 from CD plus > all updates so far". > > 2. Make GCC mainline bootstrap on this machine, preferably using the > scripts in gcc/contrib/regression. Check that the bootstrap & test > takes less than about 3 hours. [For reference, a single 800Mhz > Pentium III can do this. A two-processor 450Mhz machine should > also be able to do it. Old obsolete hardware from the early 90s > certainly can't do it; if it turns out that all we can get is old > obsolete hardware, I'll have to change the tester so that it > doesn't have to wait for all the builds to finish, but this will > take some time.] > > 3. Set up an account so that the regression tester can log in, > preferably using SSH. This is not possible for people that are behind a firewall... Would the main tester run a script on the slave and connect to it via ssh? Or would it be possible to work the other way round: The slave asking the master whether there's work to do? > 4. Then I'll check that everything works and add the new target to the > tester. > > Typically, I find step 2 to be the tricky bit for new targets---often, > the new target doesn't build. Andreas -- Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj