From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18043 invoked by alias); 5 Dec 2001 18:52:12 -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 17989 invoked from network); 5 Dec 2001 18:52:10 -0000 Received: from unknown (HELO e31.co.us.ibm.com) (32.97.110.129) by sources.redhat.com with SMTP; 5 Dec 2001 18:52:10 -0000 Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.99.140.24]) by e31.co.us.ibm.com (8.9.3/8.9.3) with ESMTP id NAA66538; Wed, 5 Dec 2001 13:49:21 -0500 Received: from gateway.beaverton.ibm.com (gateway.beaverton.ibm.com [138.95.180.1]) by westrelay03.boulder.ibm.com (8.11.1m3/NCO v5.01) with ESMTP id fB5Iq2q167648; Wed, 5 Dec 2001 11:52:02 -0700 Received: from eng2.beaverton.ibm.com (eng2.beaverton.ibm.com [138.95.200.91]) by gateway.beaverton.ibm.com (8.10.0.Beta10/8.11.2) with ESMTP id fB5IppV22183; Wed, 5 Dec 2001 10:51:51 -0800 (PST) Received: from dyn9-47-18-192.des.beaverton.ibm.com (dyn9-47-18-192.des.beaverton.ibm.com [9.47.18.192]) by eng2.beaverton.ibm.com (8.10.0.Beta10/8.8.5/token.aware-1.2) with ESMTP id fB5IpoQ05761; Wed, 5 Dec 2001 10:51:50 -0800 (PST) Received: (from janis@localhost) by dyn9-47-18-192.des.beaverton.ibm.com (8.9.3/8.9.3) id KAA31137; Wed, 5 Dec 2001 10:55:08 -0800 Date: Wed, 05 Dec 2001 10:52:00 -0000 From: Janis Johnson To: David Edelsohn Cc: Janis Johnson , Joe Buck , gcc@gcc.gnu.org Subject: Re: build status page problem Message-ID: <20011205105507.A15791@us.ibm.com> References: <200112051821.NAA26124@makai.watson.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112051821.NAA26124@makai.watson.ibm.com>; from dje@watson.ibm.com on Wed, Dec 05, 2001 at 01:21:45PM -0500 X-SW-Source: 2001-12/txt/msg00230.txt.bz2 On Wed, Dec 05, 2001 at 01:21:45PM -0500, David Edelsohn wrote: > >>>>> Janis Johnson writes: > > Janis> The assumption is that everything on the GCC 3.0 build status page > Janis> builds with all releases of 3.0.x unless it says otherwise. So far > Janis> there's only one note otherwise, for s390-linux-gnu which is supported > Janis> beginning with 3.0.1. > > Janis> I'd prefer to keep that assumption. If there's a regression that > Janis> prevents a target from building with a particular release we can add a > Janis> note to that effect for that target. > > The problem is that we cannot tell from the page what reports we > actually have received. If we have a report that some target worked with > 3.0.1 but no report for 3.0.2, we cannot tell if it works and it may > discourage someone from testing that new release and reporting the result. > > David We don't get a flood of new reports for existing entries when a new version of GCC is released, and I don't think that such reports would be particularly useful. If there is an entry for a target and someone has problems building it on some version of 3.0.x, then they should report the problem, along with the fact that a successful build has been reported. Ideally, when a new release comes out people will build it and send in their test results, which is more useful information than the build status list. I see the build status list as initial information about whether GCC 3.0.x is known to work on a particular target. There are still a lot of variables that could prevent even the same version that was reported from building on the same target with a slightly different environment, so I hope that the existence of a target on the list doesn't prevent new testing of it for new releases. It would be useful to have a script similar to contrib/test_summary to generate a message for reporting a successful build. Use of that script would ensure that we get all of the relevant information in a report of a successful build, including the configure flags to know whether all languages were built, and versions of other relevant software on a GNU/Linux system. Janis