On 04/09/2025 18:36, Collin Funk wrote:
Bruno Haible <br...@clisp.org> writes:
On 2025-08-24 I wrote:
Today's CI reports a test failure
FAIL: tests/fold/fold-spaces
on several systems:
- Alpine Linux,
- macOS 13..15,
- FreeBSD 14.
Sorry for the incorrect reporting: macOS 13 and 14 failed with a fold-nbsp
failure (bug #79300), not a fold-spaces failure.
As of today, the failures on macOS 13 and 14 are fixed. The failures on
- Alpine Linux,
- macOS 15,
- FreeBSD 14
are still present in today's CI run.
Yep, I was planning on fixing this one next. So them failing is
expected.
No worries about the slightly wrong platform list. I could reproduce
them just fine.
My thinking is that the only portable test is ASCII space or TAB, since
POSIX only requires those be treated as blank characters. I think it is
fine to leave the current tests under a check for $host_os being gnu.
You might be able to use the uniq trick
to determine if a character is blank?
https://bugs.gnu.org/cgi/79300#32
cheers,
Padraig
