X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=contrib%2Fsb-introspect%2Ftest-driver.lisp;h=e6bee2e088388c78f7c806babefc85b1d5af8013;hb=7169796933b86601eaf70d3a9064600730cb2b40;hp=810a295f1fea5ef4704a0167966d71658031319c;hpb=06c288327bb8ea3a9534c63c0a8a909445a62054;p=sbcl.git diff --git a/contrib/sb-introspect/test-driver.lisp b/contrib/sb-introspect/test-driver.lisp index 810a295..e6bee2e 100644 --- a/contrib/sb-introspect/test-driver.lisp +++ b/contrib/sb-introspect/test-driver.lisp @@ -12,6 +12,12 @@ (in-package :sb-introspect-test) +(defmacro deftest* ((name &key fails-on) form &rest results) + `(progn + (when (sb-impl::featurep ',fails-on) + (pushnew ',name sb-rt::*expected-failures*)) + (deftest ,name ,form ,@results))) + (deftest function-lambda-list.1 (function-lambda-list 'cl-user::one) (cl-user::a cl-user::b cl-user::c)) @@ -293,16 +299,21 @@ t) ;;; Skip the whole damn test on GENCGC PPC -- the combination is just -;;; to flaky for this to make too much sense. -;; #-(and ppc gencgc) - -;;; It appears that this test can fail due to systematic issues (possibly -;;; with the C compiler used) which we cannot detect based on *features*. -;;; Until this issue has been fixed, I am disabling this test entirely to -;;; to allow installation of the contrib on affected builds. C.f. lp1057631. -;;; --DFL -#-gencgc -(deftest allocation-information.4 +;;; 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 +;;; *features*. Until this issue has been fixed, I am marking this test +;;; as failing on Windows to allow installation of the contrib on +;;; affected builds, even if the underlying issue is (possibly?) not even +;;; strictly related to windows. C.f. lp1057631. --DFL +;;; +(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 (or :ppc :sparc) :gencgc))) #+gencgc (tai #'cons :heap ;; FIXME: This is the canonical GENCGC result. On PPC we sometimes get