From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 33699 invoked by alias); 26 Nov 2018 16:51:19 -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 33680 invoked by uid 89); 26 Nov 2018 16:51:17 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=unfortunate, regret, dear, encrypted 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 ESMTP; Mon, 26 Nov 2018 16:51:16 +0000 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 7A935307EAB0; Mon, 26 Nov 2018 16:51:15 +0000 (UTC) Received: from localhost (unused-10-15-17-196.yyz.redhat.com [10.15.17.196]) by smtp.corp.redhat.com (Postfix) with ESMTP id 25F2C100034A; Mon, 26 Nov 2018 16:51:14 +0000 (UTC) From: Sergio Durigan Junior To: Rainer Orth Cc: gdb-buildbot@sergiodj.net, gdb-patches@sourceware.org Subject: Re: Oh dear. I regret to inform you that commit 970d89d8fdd84b31decaf3bd84e785aad057ea32 might be unfortunate References: <970d89d8fdd84b31decaf3bd84e785aad057ea32-master-breakage@gdb-build> <87sgzu70f2.fsf@redhat.com> Date: Mon, 26 Nov 2018 16:51:00 -0000 In-Reply-To: (Rainer Orth's message of "Thu, 22 Nov 2018 10:52:41 +0100") Message-ID: <87h8g33hq5.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2018-11/txt/msg00440.txt.bz2 On Thursday, November 22 2018, Rainer Orth wrote: > Hi Sergio, Hey Rainer, >> Yeah, coincidentally (or not) I noticed the exact same thing, and I'm >> working on fixing this issue. It doesn't affect just the Solaris >> builders; it also affects the Fedora mingw32 builder (for example). >> I've manually fixed it for now (i.e., if there is another build >> breakage, you will see notifications for Solaris as well), and I'm >> working to fix the underlying issue. > > excellent, thanks. Just a quick heads-up: the fix worked, and now whenever a breakage is fixed, the Solaris builders will be "clean" to report a possible future breakage automatically. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/