From 9eb801f6a320f02c222624fc0dc58167f20bcc17 Mon Sep 17 00:00:00 2001
From: Raymond Toy <toy.raymond@gmail.com>
Date: Wed, 15 Feb 2023 13:01:43 -0800
Subject: [PATCH] Disable issue.41.1 when running CI

This test was previously disabled only for Linux when running the CI.
However, it's now also failing when running the CI for Darwin.  Thus
disable it whenever we're running the CI.

I just manually tested this on my Linux and Mac boxes.  This test
passes without any problem.  Not sure what's going on.
---
 tests/issues.lisp | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/tests/issues.lisp b/tests/issues.lisp
index 9bcfed480..89484ab5a 100644
--- a/tests/issues.lisp
+++ b/tests/issues.lisp
@@ -416,9 +416,12 @@
 ;; running a pipeline with linux, but otherwise enable it.  The
 ;; pipeline defines the envvar GITLAB_CI so check for that.
 ;;
+;; This also fails on Darwin CI now.  Let's just disable the test if
+;; running on CI.
+;;
 ;; It would be better if lisp-unit had a way of marking tests as known
 ;; failures, but it doesn't.
-#+#.(cl:if (cl:and (ext:featurep :linux) (unix:unix-getenv "GITLAB_CI")) '(or) '(and))
+#+#.(cl:if (cl:and (unix:unix-getenv "GITLAB_CI")) '(or) '(and))
 (define-test issue.41.1
     (:tag :issues)
   (issue-41-tester unix:sigstop))
-- 
GitLab