[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Failures in ‘threads.test’

From: Ludovic Courtès
Subject: Failures in ‘threads.test’
Date: Tue, 29 Mar 2011 23:47:36 +0200
User-agent: Gnus/5.110013 (No Gnus v0.13) Emacs/23.3 (gnu/linux)

Hi Dale,

An easy answer, but there’s some truth in it:

<address@hidden> 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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]