From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Failures in ‘threads.test’
Date: Tue, 29 Mar 2011 23:47:36 +0200 [thread overview]
Message-ID: <87zkoda9af.fsf@gnu.org> (raw)
In-Reply-To: 20110329130306.JE800.93088.root@cdptpa-web21-z02
Hi Dale,
An easy answer, but there’s some truth in it:
<dsmich@roadrunner.com> writes:
> With guile at v2.0.0-134-g38c50a9, I'm getting a couple of failures in threads.test on my single core Debian Squeeze machine:
>
> FAIL: threads.test: lock-mutex: timed locking succeeds if mutex unlocked within timeout
This one may be sensitive to load. Can you try changing
(+ (current-time) 2) to (+ (current-time) 5)?
> FAIL: threads.test: mutex-ownership: mutex with owner not retained (bug #27450)
This one is GC-sensitive. It’s already kludged at length to improve the
chances of success, but I don’t know how to improve the situation. It
could throw unresolved instead of failing, but that doesn’t really
help...
Thanks,
Ludo’.
next prev parent reply other threads:[~2011-03-29 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 13:03 (no subject) dsmich
2011-03-29 21:47 ` Ludovic Courtès [this message]
2011-03-30 1:27 ` Failures in ‘threads.test’ dsmich
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=87zkoda9af.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).