On 19/09/2025 01:56, William Bader wrote:
CentOS 7 has a failure in "tests/fold/fold-zero-width" about "fold didn't diagnose
ENOSPC".
Ah write-errors.sh uses a similar pattern, but with a higher mem limit.
The attached hopefully addresses the issue.
I tried to repro in a centos 6.10 podman container,
but the test passed there with the lower limit.
Anyway the higher limit is better for consistency.
cheers,
Padraig
From 3291e95f0d82fa6d87942c1937c655887a5be10e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?P=C3=A1draig=20Brady?= <[email protected]>
Date: Sat, 20 Sep 2025 16:10:16 +0100
Subject: [PATCH] tests: avoid false failure on centos 5,6,7
* tests/fold/rold.zero-width.sh: Increase vm limit to avoid
failures on centos 5,6,7. Match the limit used in write-errors.sh
as per commit v9.5-255-g0bd149403
---
tests/fold/fold-zero-width.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/fold/fold-zero-width.sh b/tests/fold/fold-zero-width.sh
index f69d89f13..b876473c7 100755
--- a/tests/fold/fold-zero-width.sh
+++ b/tests/fold/fold-zero-width.sh
@@ -52,7 +52,7 @@ vm=$(get_min_ulimit_v_ fold /dev/null) && {
# \303 results in EILSEQ on input
for c in '\n' '\0' '\303'; do
tr '\0' "$c" < /dev/zero | timeout 10 $SHELL -c \
- "(ulimit -v $(($vm+8000)) && fold 2>err >/dev/full)"
+ "(ulimit -v $(($vm+12000)) && fold 2>err >/dev/full)"
{ test $? = 124 || ! grep 'space' err >/dev/null; } &&
{ fail=1; cat err; echo "fold didn't diagnose ENOSPC" >&2; }
done
--
2.50.1
