From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14878 invoked by alias); 13 Sep 2009 22:49:09 -0000 Received: (qmail 14869 invoked by uid 22791); 13 Sep 2009 22:49:09 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_JMF_BL,SPF_PASS X-Spam-Check-By: sourceware.org Received: from vexpert.dbai.tuwien.ac.at (HELO vexpert.dbai.tuwien.ac.at) (128.131.111.2) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 13 Sep 2009 22:49:05 +0000 Received: from acrux.dbai.tuwien.ac.at (acrux.dbai.tuwien.ac.at [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id 7C8331E085; Mon, 14 Sep 2009 00:48:59 +0200 (CEST) Received: by acrux.dbai.tuwien.ac.at (Postfix, from userid 1203) id 491691005D; Mon, 14 Sep 2009 00:49:04 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by acrux.dbai.tuwien.ac.at (Postfix) with ESMTP id 3A3AC10059; Mon, 14 Sep 2009 00:49:04 +0200 (CEST) Date: Sun, 13 Sep 2009 22:49:00 -0000 From: Gerald Pfeifer To: "H.J. Lu" , Laurent GUERBY cc: gcc@gcc.gnu.org Subject: Re: Annoucing regressions and bootstrap fail? (was: Bootstrap broken on sparc-linux trunk between 145310:145425 because of new genattrtab.c va_arg (p, HOST_WIDE_INT) warning) In-Reply-To: <1238946634.10782.116.camel@localhost> Message-ID: References: <1238923527.10782.51.camel@localhost> <6dc9ffc80904050825k5d73c881u94114888269f06fb@mail.gmail.com> <1238946634.10782.116.camel@localhost> User-Agent: Alpine 1.99 (LSU 1142 2008-08-13) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-09/txt/msg00236.txt.bz2 On Sun, 5 Apr 2009, Laurent GUERBY wrote: >>> I'm thinking of changing my auto tester to report a broken bootstrap >>> (the first time a bootstrap fails), is there a normalized way to >> report such failures to gcc-testresults@ or gcc@? >> I report it to gcc-regression@. > It's documented by http://gcc.gnu.org/lists.html as "read-only": > > gcc-regression is a read-only moderate volume list where regression > results for the GCC compilers are posted. > > So I thought one couldn't post to it. Indeed, that looks like a mistake in the documentation of this list. > If there's consensus that's the right place to send automatic regression > and bootstrap fail reports I'll do that then. So far HJ and Geoff seem to be the main (if not sole) contributors to that least, but that sounds reasonable. For now I have applied the patch below to our web site; if there are further improvements you can think of -- don't be shy! :-) Gerald Index: lists.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/lists.html,v retrieving revision 1.103 diff -u -3 -p -r1.103 lists.html --- lists.html 4 Nov 2007 12:26:48 -0000 1.103 +++ lists.html 13 Sep 2009 22:45:55 -0000 @@ -69,6 +69,10 @@ before subscribing< gcc-testresults is a moderate volume list where test results for the GCC compilers are posted. +
  • gcc-regression + is a moderate volume list where regression results for the GCC compilers + are posted.
    • +
  • libstdc++ is the main discussion and development list for the standard C++ library (libstdc++-v3). Patches to libstdc++-v3 should be sent to @@ -110,10 +114,6 @@ before subscribing< is a read-only, relatively low volume list which tracks checkins to the GCC webpages CVS repository.
    • -
  • gcc-regression - is a read-only moderate volume list where regression - results for the GCC compilers are posted.
    • -
  • gccadmin is a read-only moderate volume list where output from cron jobs run by the gccadmin account on