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.

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.

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

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"