From a682600e6469735185553ac21c25c50686c54abb Mon Sep 17 00:00:00 2001 From: Nikodemus Siivola Date: Thu, 10 Nov 2011 16:08:55 +0200 Subject: [PATCH] tweak threads.impure.lisp tests * Enable (:CONDITION-WAIT :DEADLINES :LP-512914) outside futex platforms. * Mark :BACKTRACE as broken on Darwin after all, still. --- tests/threads.impure.lisp | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/tests/threads.impure.lisp b/tests/threads.impure.lisp index 75bb628..141cec0 100644 --- a/tests/threads.impure.lisp +++ b/tests/threads.impure.lisp @@ -1042,8 +1042,7 @@ ;;; Make sure that a deadline handler is not invoked twice in a row in ;;; CONDITION-WAIT. See LP #512914 for a detailed explanation. ;;; -(with-test (:name (:condition-wait :deadlines :LP-512914) - :skipped-on '(not :sb-futex)) +(with-test (:name (:condition-wait :deadlines :LP-512914)) (let ((n 2) ; was empirically enough to trigger the bug (mutex (sb-thread:make-mutex)) (waitq (sb-thread:make-waitqueue)) @@ -1174,7 +1173,7 @@ (format t "infodb test done~%") -(with-test (:name :backtrace) +(with-test (:name :backtrace :broken-on :darwin) ;; Printing backtraces from several threads at once used to hang the ;; whole SBCL process (discovered by accident due to a timer.impure ;; test misbehaving). The cause was that packages weren't even -- 1.7.10.4