From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: GDB Development <gdb@sourceware.org>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [ANNOUNCEMENT] GDB BuildBot
Date: Tue, 27 Jan 2015 20:05:00 -0000 [thread overview]
Message-ID: <87ppa0npjy.fsf@redhat.com> (raw)
In-Reply-To: <1422350653.4858.35.camel@bordewijk.wildebeest.org> (Mark Wielaard's message of "Tue, 27 Jan 2015 10:24:13 +0100")
On Tuesday, January 27 2015, Mark Wielaard wrote:
> On Wed, 2015-01-21 at 17:53 -0500, Sergio Durigan Junior wrote:
>> First, thanks to Mark Wielaard for setting up a Debian Wheezy x86_64
>> machine as one of our buildslaves!
>
> BTW. I saw more spurious failures on this setup than on the other
> buildbot slaves. After lots of digging it turns out that all released
> versions of dejagnu have a bug that causes spurious fails in some cases
> on SMP machines...
>
> The patch to fix that was posted back in 2005, and was picked up by
> fedora in 2006. Which explains why I could reproduce it on my Fedora or
> RHEL setups. But at least Debian based distros don't have this patch
> yet, since it is not in the latest 1.5.1 dejagnu release yet.
>
> It is in upstream dejagnu git now:
> https://lists.gnu.org/archive/html/dejagnu/2011-03/msg00019.html
>
> Full writeup is in the Debian bug report:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776362
>
> If you are running a buildbot slave (or just make gdb-check) and run a
> machine with multiple cores you might want to check that you have the
> above patch applied to prevent some spurious FAILs.
Wow :-). Thanks for the investigation, Mark. It is probably worth
putting this info in the wiki:
<http://sourceware.org/gdb/wiki/BuildBot>. I will put it there later
(if you don't beat me to it).
Cheers,
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2015-01-27 16:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 23:43 Sergio Durigan Junior
2015-01-15 12:13 ` Joel Brobecker
2015-01-15 19:36 ` Sergio Durigan Junior
2015-01-21 22:53 ` Sergio Durigan Junior
2015-01-22 18:15 ` Eli Zaretskii
2015-01-22 18:38 ` Sergio Durigan Junior
2015-01-22 18:43 ` Eli Zaretskii
2015-01-22 18:57 ` Sergio Durigan Junior
2015-01-22 19:25 ` Eli Zaretskii
2015-01-22 19:55 ` Eli Zaretskii
2015-01-22 20:32 ` Sergio Durigan Junior
2015-01-22 20:39 ` Eli Zaretskii
2015-01-22 20:48 ` Eli Zaretskii
2015-01-22 21:32 ` Eli Zaretskii
2015-01-22 22:28 ` Sergio Durigan Junior
2015-01-22 22:34 ` Doug Evans
2015-01-23 9:06 ` Sergio Durigan Junior
2015-01-23 9:57 ` Eli Zaretskii
2015-01-23 9:09 ` Eli Zaretskii
2015-01-23 10:14 ` Pedro Alves
2015-01-23 11:01 ` Eli Zaretskii
2015-01-23 16:16 ` Andreas Schwab
2015-01-23 17:47 ` Eli Zaretskii
2015-01-22 21:46 ` Sergio Durigan Junior
2015-01-23 10:41 ` Pedro Alves
2015-01-23 10:46 ` Eli Zaretskii
2015-01-23 14:25 ` Pedro Alves
2015-01-27 16:42 ` Mark Wielaard
2015-01-27 20:05 ` 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=87ppa0npjy.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=mjw@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