From: Pedro Alves <palves@redhat.com>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Racy failures on gdb.base/gdbinit-history.exp (native-extended-gdbserver/-m64)
Date: Thu, 10 Sep 2015 13:44:00 -0000 [thread overview]
Message-ID: <55F18922.3070202@redhat.com> (raw)
In-Reply-To: <CA+C-WL9zL3i_j573K03GCTvE9EkJzh_HDx-Fx=3L5Pn=-NPwpw@mail.gmail.com>
On 08/18/2015 12:29 AM, Patrick Palka wrote:
> On Mon, Aug 17, 2015 at 4:10 PM, Patrick Palka <patrick@parcs.ath.cx> wro
>> But I just locally installed dejagnu from git, and have had the above
>> command running for about 30 minutes (after confirming that my local
>> copy, not system copy, of dejagnu is being used by the testsuite), and
>> fortunately, I could no longer reproduce these FAILs. So it seems
>> that your changes to dejagnu fixed this spurious FAIL as well. I'll
>> let it keep spinning though, just in case.
> Anyway, with dejagnu from git I could no longer reproduce these FAILs
> after 3 straight hours of repeatedly running the test.
(almost a month passed somehow, but ...) Hurray!
The DejaGnu patch has been backported to Fedora 21-23 meanwhile, so hopefully
these issues will start to fade away. Someone might want to contact the
debian / ubuntu dejagnu maintainers to do the same.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-09-10 13:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 19:28 [PATCH] Don't truncate the history file when history size is unlimited Patrick Palka
2015-06-15 15:25 ` Pedro Alves
2015-06-15 16:01 ` Patrick Palka
2015-06-15 16:18 ` Pedro Alves
2015-06-16 14:53 ` Patrick Palka
2015-06-16 15:00 ` Patrick Palka
2015-06-17 13:14 ` Pedro Alves
2015-06-17 12:46 ` Pedro Alves
2015-07-23 18:42 ` Racy failures on gdb.base/gdbinit-history.exp (native-extended-gdbserver/-m64) (was: Re: [PATCH] Don't truncate the history file when history size is unlimited) Sergio Durigan Junior
2015-07-23 19:33 ` Patrick Palka
2015-07-24 14:03 ` Patrick Palka
2015-07-24 14:16 ` Patrick Palka
2015-08-13 15:18 ` Patrick Palka
2015-08-13 22:28 ` Racy failures on gdb.base/gdbinit-history.exp (native-extended-gdbserver/-m64) Sergio Durigan Junior
2015-08-13 23:26 ` Pedro Alves
2015-08-14 0:46 ` Sergio Durigan Junior
2015-08-17 13:16 ` Patrick Palka
2015-08-17 13:28 ` Patrick Palka
2015-08-17 14:03 ` Pedro Alves
2015-08-17 20:10 ` Patrick Palka
2015-08-17 23:29 ` Patrick Palka
2015-09-10 13:44 ` Pedro Alves [this message]
2015-09-10 15:30 ` Sergio Durigan Junior
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=55F18922.3070202@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=patrick@parcs.ath.cx \
--cc=sergiodj@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).