From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 70367 invoked by alias); 10 Jul 2015 14:04:13 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 69551 invoked by uid 89); 10 Jul 2015 14:04:13 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ig0-f176.google.com Received: from mail-ig0-f176.google.com (HELO mail-ig0-f176.google.com) (209.85.213.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 10 Jul 2015 14:04:12 +0000 Received: by igcqs7 with SMTP id qs7so13419744igc.0 for ; Fri, 10 Jul 2015 07:04:10 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.43.196 with SMTP id y4mr3703673igl.14.1436537049839; Fri, 10 Jul 2015 07:04:09 -0700 (PDT) Received: by 10.36.108.21 with HTTP; Fri, 10 Jul 2015 07:04:09 -0700 (PDT) In-Reply-To: <20150710034255.GB7406@adacore.com> References: <20150709232141.GA7406@adacore.com> <20150710034255.GB7406@adacore.com> Date: Fri, 10 Jul 2015 14:04:00 -0000 Message-ID: Subject: Re: GDB 7.9.90 available for testing From: David Edelsohn To: Joel Brobecker Cc: GDB Patches Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2015-07/txt/msg00322.txt.bz2 On Thu, Jul 9, 2015 at 11:42 PM, Joel Brobecker wrote: >> I'm not certain if the baselines truly are accurate for all >> buildslaves, but it seems strange to create a release when the >> buildbot testsuite results show patches causing new failures. > > To me, you are saying the same thing, and I don't disagree with you. > I said I didn't know that the buildBots were showing regressions. > Of course I would have held the creation of the branch if I had > known about this. But I didn't, and so here we are. Now we all know, > and the only way forward is to look at those regressions, and decide > what to do. We can and will delay the release if we have to. Joel, We are agreeing. I was trying to provide some additional information about interpretation of the buildbot status. I am note two things about the buildbots: 1) Their color-coded "regression status" apparently is a comparison of the testsuite between a "base" run and the current run. This is due to few or no targets have completely clean testsuite runs to consider "green". Because there has been some adjustment and tweaking while buildbots were added, the first run was not necessarily the ideal one to choose as the "base" run, i.e., "regressions" may be due to changes in the measurements after the first "base" run, not new failing tests. 2) Separate from the "regression" status, a quick inspection of some testsuite output in the buildbots show the introduction of new errors with recent commits. Even if the overall regression status is not an accurate measure of the state of GDB on those targets, the change in regression status that is not monotonic reduction in regressions in preparation for a release is disappointing. I'm not demanding STOP SHIP. GDB may not necessarily be in a bad state for a release. I don't know how this compares to the regression status of previous releases. I hope that GDB developers will become more aware of the effects of their patches on multiple targets. Thanks, David