Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [pushed] Improve gdb.threads/attach-many-short-lived-threads.exp timeout handling
Date: Mon, 09 Feb 2015 21:55:00 -0000	[thread overview]
Message-ID: <CADPb22Q8ScnOfeCPbnzEJQaY58Pc7px_6irrZmV3QhMTeOfwSQ@mail.gmail.com> (raw)
In-Reply-To: <1423225537-26694-1-git-send-email-palves@redhat.com>

On Fri, Feb 6, 2015 at 4:25 AM, Pedro Alves <palves@redhat.com> wrote:
> The buildbot shows that this test is still racy, and occasionally
> fails with time outs on some machines.  I'd like to get major issues
> with load out of the way.

Thanks for fixing this.

btw, how often do you run the testsuite in parallel?
I see such load related issues all the time that way.
[e.g., checkpoint.exp, gdb-sigterm.exp, et.al.]


  reply	other threads:[~2015-02-09 21:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 12:25 Pedro Alves
2015-02-09 21:55 ` Doug Evans [this message]
2015-02-09 23:06   ` Pedro Alves

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=CADPb22Q8ScnOfeCPbnzEJQaY58Pc7px_6irrZmV3QhMTeOfwSQ@mail.gmail.com \
    --to=dje@google.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