From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15377 invoked by alias); 15 Jan 2018 15:18:08 -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 13242 invoked by uid 89); 15 Jan 2018 15:18:05 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy= 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, 15 Jan 2018 15:18:04 +0000 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D2D365B319; Mon, 15 Jan 2018 15:18:02 +0000 (UTC) Received: from localhost (unused-10-15-17-193.yyz.redhat.com [10.15.17.193]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A47BE60CAC; Mon, 15 Jan 2018 15:17:14 +0000 (UTC) From: Sergio Durigan Junior To: Andreas Arnez Cc: Pedro Alves , gdb-patches@sourceware.org, David Edelsohn , Edjunior Machado Subject: Re: [pushed + testcase] Re: [PATCH] Fix GDB hang with remote after error from resume References: <7eccd434-6f47-590e-e53f-32076e99c98b@redhat.com> Date: Mon, 15 Jan 2018 15:18:00 -0000 In-Reply-To: (Andreas Arnez's message of "Mon, 15 Jan 2018 15:43:47 +0100") Message-ID: <87r2qr5ezc.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2018-01/txt/msg00271.txt.bz2 On Monday, January 15 2018, Andreas Arnez wrote: > On Fri, Jan 12 2018, Pedro Alves wrote: > >> I've pushed in your patch to both master and 8.1, along with this >> follow up commit adding a testcase. > > Great, thanks! > > Sergio, now that this is in, we should be able to re-activate the > reporting for the s390 (and Power) Buildbots, right? Thanks for taking care of this, Andreas. I had to cancel all pending builds for the 3 s390x builders, because they had more than 130 builds in the queue each. Now, I'll monitor the next builds and check if the problem still persists. If not, then I can certainly re-activate the notifications for s390x. As for the PPC builders, Yao mentioned that there are probably other issues to be solved. I know Edjunior is also testing your fix on PPC as I write this e-mail, so I'll wait for their opinions here. 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/