From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 121644 invoked by alias); 10 Jul 2015 15:08:56 -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 121634 invoked by uid 89); 10 Jul 2015 15:08:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 10 Jul 2015 15:08:55 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (Postfix) with ESMTPS id 97066B6F47; Fri, 10 Jul 2015 15:08:53 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t6AF8pCC017982; Fri, 10 Jul 2015 11:08:52 -0400 Message-ID: <559FE003.5000205@redhat.com> Date: Fri, 10 Jul 2015 15:08:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: David Edelsohn CC: Joel Brobecker , GDB Patches Subject: Re: GDB 7.9.90 available for testing References: <20150709232141.GA7406@adacore.com> <20150710034255.GB7406@adacore.com> <559FD7C6.2060502@redhat.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-07/txt/msg00328.txt.bz2 On 07/10/2015 03:56 PM, David Edelsohn wrote: > My concern is more about GDB on Linux on z Systems and even GDB on > x86-64, not AIX. AIX is weird. > > Shouldn't the buildbots for z Series and x86-64 be green before a release? Ideally yes, but until the racy tests issue is fixed/kfailed and another set of old known failures is kfail/xfailed, that can't happen. I don't think any buildbot slave has ever been stably green yet; they weren't green to start with. It used to be much worse a few months ago, we're getting there, but it requires effort, and we could use all the help we can get. The buildbots are quite useful, but we can't rely on greenness alone to determine release-readyness at the moment. Thanks, Pedro Alves