GNU bug report logs - #76550
30.1; Test failure for fns-tests-collate-strings with musl libc

Previous Next

Package: emacs;

Reported by: Ulrich Müller <ulm <at> gentoo.org>

Date: Tue, 25 Feb 2025 11:53:01 UTC

Severity: minor

Found in version 30.1

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log


Message #11 received at 76550 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ulrich Müller <ulm <at> gentoo.org>
Cc: 76550 <at> debbugs.gnu.org
Subject: Re: bug#76550: 30.1;
 Test failure for fns-tests-collate-strings with musl libc
Date: Tue, 25 Feb 2025 18:29:19 +0200
> From: Ulrich Müller <ulm <at> gentoo.org>
> Date: Tue, 25 Feb 2025 12:49:49 +0100
> 
> 1 unexpected results:
>    FAILED  fns-tests-collate-strings  ((should-error (string-collate-equalp "xyzzy" "xyzzy" "en_XY.UTF-8")) :form (string-collate-equalp "xyzzy" "xyzzy" "en_XY.UTF-8") :value t :fail-reason "did not signal an error")
> 
> make[3]: *** [Makefile:185: src/fns-tests.log] Error 1
> 
> 
> The problem is that (string-collate-equalp "xyzzy" "xyzzy" "en_XY.UTF-8")
> doesn't signal an error with musl libc. This is because newlocale(3)
> always succeeds, regardless of the string passed as its second argument.
> 
> (Note that bug #62420 had addressed a failure of the same test, and the
> fix was to replace "en_DE.UTF-8" with "en_XY.UTF-8". This definitely
> isn't enough to fix the problem on musl.)

I think this quirk is glibc-specific, and the test should be disabled
in the musl build.




This bug report was last modified 82 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.