From 939134b87821a32b84a2f14a48ea705eb0d49d7c Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Sun, 9 Nov 2025 21:14:38 +0100 Subject: Revert "testsuite: disable testcases with Valgrind only when detecting the fmsbw.de CI runner" This reverts commit 092f7d9919d9572219b7bf516933c37180e6f400. Turns out that the "Memory limiting" test cases won't even successfully run on my PC under Valgrind. --- tests/testsuite.at | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'tests') diff --git a/tests/testsuite.at b/tests/testsuite.at index 38035a8..ec6b034 100644 --- a/tests/testsuite.at +++ b/tests/testsuite.at @@ -378,7 +378,7 @@ AT_CLEANUP AT_SETUP([Memory limiting]) # FIXME: Requires too much time and memory at least when running in a CI job on my fmsbw.de server # (.fmsbw/10-freebsd14-sciteco). -AT_SKIP_IF([test $at_arg_valgrind != false -a "$FMSBW_CI" = 1]) +AT_SKIP_IF([test $at_arg_valgrind != false]) TE_CHECK([[50*1000*1000,2EJ <[a> !]!]], 1, ignore, ignore) AT_CLEANUP @@ -500,7 +500,7 @@ AT_CLEANUP AT_SETUP([Memory limiting during spawning]) # FIXME: Requires too much time and memory at least when running in a CI job on my fmsbw.de server # (.fmsbw/10-freebsd14-sciteco). -AT_SKIP_IF([test $at_arg_valgrind != false -a "$FMSBW_CI" = 1]) +AT_SKIP_IF([test $at_arg_valgrind != false]) # This might result in an OOM if memory limiting is not working TE_CHECK([[50*1000*1000,2EJ 0,128ED @EC'dd if=/dev/zero']], 1, ignore, ignore) AT_CLEANUP -- cgit v1.2.3