Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Fix racy FAILs of sigall-reverse.exp (and more)
Date: Tue, 03 Feb 2015 15:27:00 -0000	[thread overview]
Message-ID: <54D0E8E4.8090407@redhat.com> (raw)
In-Reply-To: <1422292759-22307-1-git-send-email-palves@redhat.com>

On 01/26/2015 06:19 PM, Pedro Alves wrote:
> As can be seen in the buildbot results sent to the gdb-testers@ list,
> sigall-reverse.exp is occasionally failing.
> 
> With my WIP all-stop-on-stop-of-non-stop series some other tests were
> failing in a similar manner, which was what prompted me to look at
> this in the first place.
> 
> This series fixes the root problems.  sigall-reverse.exp seems to be
> robust for me now.
> 
> Tested on x86_64 Fedora 20, native and gdbserver.
> 
> Given the 'query' change that exposed these bugs is in 7.9, I'd like
> to see this fixed there too.  My idea would be to push this into
> master, give it a few days of buildbot exposure, and if all goes well,
> push it to the branch.

I've pushed the series to master now.

Thanks,
Pedro Alves


      parent reply	other threads:[~2015-02-03 15:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 17:32 Pedro Alves
2015-01-26 17:19 ` [PATCH 2/3] When disabling target async, remove all target event sources from the event loop Pedro Alves
2015-01-26 17:46 ` [PATCH 1/3] Fix up some target is-async vs can-async confusions Pedro Alves
2015-01-26 19:16 ` [PATCH 3/3] Simplify event-loop core, remove two-step event processing Pedro Alves
2015-02-03 22:48   ` Patrick Palka
2015-02-04 10:51     ` Pedro Alves
2015-02-04 17:34     ` Alex Velenko
2015-02-04 18:18       ` Pedro Alves
2015-02-04  9:49   ` Sergio Durigan Junior
2015-02-03 15:27 ` Pedro Alves [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=54D0E8E4.8090407@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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