Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: Pedro Alves <palves@redhat.com>,
	 gdb-patches@sourceware.org,  David Edelsohn <dje.gcc@gmail.com>,
	 Edjunior Machado <emachado@redhat.com>
Subject: Re: [pushed + testcase] Re: [PATCH] Fix GDB hang with remote after error from resume
Date: Mon, 15 Jan 2018 15:18:00 -0000	[thread overview]
Message-ID: <87r2qr5ezc.fsf@redhat.com> (raw)
In-Reply-To: <m31sir5gik.fsf@oc1027705133.ibm.com> (Andreas Arnez's message of	"Mon, 15 Jan 2018 15:43:47 +0100")

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/


      parent reply	other threads:[~2018-01-15 15:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 16:56 Andreas Arnez
2018-01-12 19:11 ` [pushed + testcase] " Pedro Alves
2018-01-15 14:43   ` Andreas Arnez
2018-01-15 14:53     ` Yao Qi
2018-01-15 15:22       ` Andreas Arnez
2018-01-15 16:10         ` Yao Qi
2018-01-15 17:37       ` Edjunior Machado
2018-01-15 18:17         ` Pedro Alves
2018-01-15 20:11           ` Sergio Durigan Junior
2018-01-15 15:18     ` Sergio Durigan Junior [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r2qr5ezc.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=emachado@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox