test/common: skip google tests which create core dumps in test_interval_set

CI Pipelines are being broken because this test is creating a number of core dumps. This
does not make the test fail, but it does create some core dumps. This appears to be
breaking something in the CI pipeline.  This commit is a workaround and I will find a
better solution later.

Fixes: https://tracker.ceph.com/issues/70543
Signed-off-by: Alex Ainscow <aainscow@uk.ibm.com>

diff --git a/src/test/common/test_interval_set.cc b/src/test/common/test_interval_set.cc
index 75d4c83da2e8c3cb9c294a16a666d01fa520efa2..f415d6127a8b6836763d04382134ce7c5377351d 100644 (file)
--- a/src/test/common/test_interval_set.cc
+++ b/src/test/common/test_interval_set.cc
@@ -26,7 +26,10 @@ using namespace ceph;
  * if (interval set has strict=true) expect that ceph will panic.
  * else expect that ceph will not panic and execute the second clause.
  */
-#define ASSERT_STRICT_DEATH(s, e) if constexpr (ISet::test_strict) ASSERT_DEATH(s, ""); else { s; e; }
+// FIXME: The CI pipeline cannot cope with the core dumps that ASSERT_DEATH
+//        creates, so we need to find a better approach. Disabling to unblock.
+//#define ASSERT_STRICT_DEATH(s, e) if constexpr (ISet::test_strict) ASSERT_DEATH(s, ""); else { s; e; }
+#define ASSERT_STRICT_DEATH(s, e) if constexpr (ISet::test_strict) GTEST_SKIP(); else { s; e; }
 
 typedef uint64_t IntervalValueType;