From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18551 invoked by alias); 26 Oct 2002 10:12:17 -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 18409 invoked from network); 26 Oct 2002 10:12:13 -0000 Received: from unknown (HELO vexpert.dbai.tuwien.ac.at) (128.130.111.12) by sources.redhat.com with SMTP; 26 Oct 2002 10:12:13 -0000 Received: from pulcherrima (pulcherrima [128.130.111.23]) by vexpert.dbai.tuwien.ac.at (8.12.6/8.12.6) with ESMTP id g9QACC7m026366; Sat, 26 Oct 2002 12:12:12 +0200 (CEST) Date: Sat, 26 Oct 2002 18:20:00 -0000 From: Gerald Pfeifer To: gcc@gcc.gnu.org cc: Ben Elliston , Subject: Re: GCC regression testing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-10/txt/msg01572.txt.bz2 On 22 Oct 2002, Ben Elliston wrote: > I've been following the discussion about the lack of GCC regression > testing and decided to take on the task. Great! > http://people.redhat.com/bje/tinderbox.html We should really document this, so I went ahead an committed the following patch: Do not refer to http://gcc.gnu.org/testresults/ any longer, which has not been updated for more than a year. Add a new page on testers instead. This is just a skeleton, Ben, feel free to extend it as you see fit. And, of course, everyone else operating similar testers, please add yourself as well (or send me some details and I will do it for you). Thanks, Gerald Index: index.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v retrieving revision 1.336 diff -u -3 -p -r1.336 index.html --- index.html 4 Oct 2002 13:38:46 -0000 1.336 +++ index.html 26 Oct 2002 10:09:21 -0000 @@ -128,10 +128,11 @@ snapshots.

We strive to provide regular, high quality releases, which we want to work well on a variety -of native (including GNU/Linux) and cross targets. To that end, we use an -extensive test suite as well -as various benchmark suites -and automated testers to maintain and improve quality.

+of native (including GNU/Linux) and cross targets. +To that end, we use an extensive test +suite and automated regression testers as well +as various benchmark suites and automated testers +to maintain and improve quality.