X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=tests%2Ftimer.impure.lisp;h=3cea11c68394159106a317a5c96dd1414cdd6677;hb=5cf3c4259d529e180d75d4d140f344e600d2b06b;hp=32b245e12cb4104185da50dc1e198832593bb338;hpb=62e8cf70b09b73b8a94c303c28d4f4721135bae9;p=sbcl.git

diff --git a/tests/timer.impure.lisp b/tests/timer.impure.lisp
index 32b245e..3cea11c 100644
--- a/tests/timer.impure.lisp
+++ b/tests/timer.impure.lisp
@@ -165,7 +165,9 @@
         (loop
            (assert (eq wanted (subtypep type1 type2))))))))
 
-#+sb-thread
+;;; Disabled. Hangs occasionally at least on x86. See comment before
+;;; the next test case.
+#+(and nil sb-thread)
 (with-test (:name (:timer :parallel-unschedule))
   (let ((timer (sb-ext:make-timer (lambda () 42) :name "parallel schedulers"))
         (other nil))
@@ -195,6 +197,10 @@
 ;;;; it seems plausible that the fast timers simply fill up the interrupt
 ;;;; queue completely. (On some occasions the process unwedges itself after
 ;;;; a few minutes, but not always.)
+;;;;
+;;;; FIXME: Another failure mode on Linux: recursive entries to
+;;;; RUN-EXPIRED-TIMERS blowing the stack.
+#+nil
 (with-test (:name (:timer :schedule-stress))
   (flet ((test ()
            (let* ((slow-timers (loop for i from 1 upto 100