From: Rob Browning <rlb@defaultvalue.org>
To: bug-guile@gnu.org
Subject: Guile 2.0.0 threads.test failure on i686 and amd64
Date: Sat, 26 Feb 2011 19:22:37 -0600 [thread overview]
Message-ID: <8762s69spu.fsf@raven.defaultvalue.org> (raw)
Make check is failing in threads.test on Debian i686 and amd64 machines
running recent Debian unstable. This is the actual error:
FAIL: threads.test: lock-mutex: timed locking succeeds if mutex
unlocked within timeout
and here are some of the relevant dependencies:
libgc: current CVS
gcc: 4.4.5-10 (i686), 4.4.5-12 (amd64)
libc: 2.11.2-10 (i686), 2.1.2-11 (amd64)
kernel: 2.6.32-5-686-bigmem, 2.6.37-1-amd64
Please let me know if I can provide additional information, or if there
are any additional tests you'd like me to run.
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next reply other threads:[~2011-02-27 1:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 1:22 Rob Browning [this message]
2011-02-27 15:13 ` Guile 2.0.0 threads.test failure on i686 and amd64 Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8762s69spu.fsf@raven.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=bug-guile@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).