From e4147a0988ad2cdfe0f7b4b1eb7a6c5c4a2ce9fa Mon Sep 17 00:00:00 2001 From: Alex Ainscow Date: Wed, 19 Mar 2025 13:59:35 +0000 Subject: [PATCH] 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 --- src/test/common/test_interval_set.cc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/test/common/test_interval_set.cc b/src/test/common/test_interval_set.cc index 75d4c83da2e8c..f415d6127a8b6 100644 --- 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; -- 2.39.5