bug#61534: closed (three Emacs tests fail in en_US.utf8 locale on Ubuntu)

[GNU bug Tracking System]

Your message dated Tue, 5 Sep 2023 17:04:02 -0700
with message-id 
<CADwFkmkiKbsF-j7fi1hmSSZhoWBWwq3jRBFbQmYp=A0_obQwgA@mail.gmail.com>
and subject line Re: bug#61534: three Emacs tests fail in en_US.utf8 locale on 
Ubuntu
has caused the debbugs.gnu.org bug report #61534,
regarding three Emacs tests fail in en_US.utf8 locale on Ubuntu
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
61534: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61534
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: three Emacs tests fail in en_US.utf8 locale on Ubuntu Date: Wed, 15 Feb 2023 10:18:08 -0800 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 If the environment variable LC_ALL is set to 'en_US.utf8', three coding system related tests fail in bleeding-edge Emacs (commit 51e3f91f50da43f18706410bf6cd096684379daa) when run on Ubuntu 22.10 with current patches. The problem goes away if LC_ALL is set to 'C', so this most likely has something to do with how Emacs reacts to the current locale.

Attached is the compressed output of 'make -j12 bootstrap && make -j12 check'.

make-check-log.txt.gz
Description: application/gzip

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#61534: three Emacs tests fail in en_US.utf8 locale on Ubuntu
>
>
>
>
> Date: 
>
> Tue, 5 Sep 2023 17:04:02 -0700
>
>
>
>
> Mattias Engdegård <mattiase@acm.org> writes:
>
> > 15 feb. 2023 kl. 20.03 skrev Eli Zaretskii <eliz@gnu.org>:
> >
> >>   FAILED  48/49  lread-tests--unescaped-char-literals (0.000455 sec) at 
> >> src/lread-tests.el:133
> >>
> >> Mattias, any ideas?
> >
> > These looks like consequences from fixing a couple of diagnostics text styling
> > bugs some time ago. Remedies have now been pushed (07a76a06f9). Thank you for
> > bringing this to my attention!
>
> I'm therefore closing this bug report.
>
>
> --- End Message ---