X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;ds=sidebyside;f=contrib%2Fsb-introspect%2Ftest-driver.lisp;h=e6bee2e088388c78f7c806babefc85b1d5af8013;hb=7169796933b86601eaf70d3a9064600730cb2b40;hp=e31b2a38ad807b344edfe098ab5e0a9e8d2a9e3f;hpb=f7ed0a1e83f34b447e621d22b6010f78171bd8ad;p=sbcl.git

diff --git a/contrib/sb-introspect/test-driver.lisp b/contrib/sb-introspect/test-driver.lisp
index e31b2a3..e6bee2e 100644
--- a/contrib/sb-introspect/test-driver.lisp
+++ b/contrib/sb-introspect/test-driver.lisp
@@ -299,7 +299,9 @@
   t)
 
 ;;; Skip the whole damn test on GENCGC PPC -- the combination is just
-;;; to flaky for this to make too much sense.
+;;; to flaky for this to make too much sense.  GENCGC SPARC almost
+;;; certainly exhibits the same behavior patterns (or antipatterns) as
+;;; GENCGC PPC.
 ;;;
 ;;; -- It appears that this test can also fail due to systematic issues
 ;;; (possibly with the C compiler used) which we cannot detect based on
@@ -311,7 +313,7 @@
 (deftest* (allocation-information.4
            ;; Ignored as per the comment above, even though it seems
            ;; unlikely that this is the right condition.
-           :fails-on (or :win32 (and :ppc :gencgc)))
+           :fails-on (or :win32 (and (or :ppc :sparc) :gencgc)))
     #+gencgc
     (tai #'cons :heap
          ;; FIXME: This is the canonical GENCGC result. On PPC we sometimes get