From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: Guile 2.0.0 threads.test failure on i686 and amd64
Date: Sun, 27 Feb 2011 16:13:02 +0100 [thread overview]
Message-ID: <87d3mdecjl.fsf@gnu.org> (raw)
In-Reply-To: 8762s69spu.fsf@raven.defaultvalue.org
Hi Rob,
Rob Browning <rlb@defaultvalue.org> writes:
> FAIL: threads.test: lock-mutex: timed locking succeeds if mutex
> unlocked within timeout
Could you change the test from ‘(+ (current-time) 2)’ to
‘(+ (current-time) 100)’?
I suppose this test is sensitive to the machine load.
Thanks,
Ludo’.
prev parent reply other threads:[~2011-02-27 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 1:22 Guile 2.0.0 threads.test failure on i686 and amd64 Rob Browning
2011-02-27 15:13 ` Ludovic Courtès [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
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=87d3mdecjl.fsf@gnu.org \
--to=ludo@gnu.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).