1.0.18.30: disable failing test in timer.impure.lisp

 * Has been failing intermittently on various platforms, apparently as
   long as it has been there. Log as bug #428.

diff --git a/BUGS b/BUGS
index e467f8b..0902dfd 100644 (file)
--- a/BUGS
+++ b/BUGS
@@ -1916,3 +1916,7 @@ generally try to check returns in safe code, so we should here too.)
 
  reported by Stelian Ionescu on sbcl-devel.
 
+428: TIMER SCHEDULE-STRESS in timer.impure.lisp fails
+
+ Failure modes vary. Core problem seems to be (?) recursive entry to
+ RUN-EXPIRED-TIMERS.

diff --git a/tests/timer.impure.lisp b/tests/timer.impure.lisp
index 32b245e..21ec58f 100644 (file)
--- a/tests/timer.impure.lisp
+++ b/tests/timer.impure.lisp
@@ -195,6 +195,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

diff --git a/version.lisp-expr b/version.lisp-expr
index 6fae4d8..537f17b 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; checkins which aren't released. (And occasionally for internal
 ;;; versions, especially for internal versions off the main CVS
 ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.18.29"
+"1.0.18.30"