GNU bug report logs - #74428
tests/printf/printf-cov failure on macOS

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Pádraig Brady <P <at> draigBrady.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#74428: closed (tests/printf/printf-cov failure on macOS)
Date: Tue, 19 Nov 2024 18:33:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 19 Nov 2024 18:31:31 +0000
with message-id <6f2cb9cb-84ad-4a7f-8796-6d42e4fe691e <at> draigBrady.com>
and subject line Re: bug#74428: tests/printf/printf-cov failure on macOS
has caused the debbugs.gnu.org bug report #74428,
regarding tests/printf/printf-cov failure on macOS
to be marked as done.

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


-- 
74428: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=74428
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Grisha Levit <grishalevit <at> gmail.com>
To: bug-coreutils <at> gnu.org
Subject: tests/printf/printf-cov failure on macOS
Date: Mon, 18 Nov 2024 23:41:46 -0500

The u4 and U8 tests in tests/printf/printf-cov.pl fail on macOS 15:

u4...
printf: test u4: stdout mismatch, comparing u4.1 (expected) and u4.O (actual)
*** u4.1	Mon Nov 18 23:30:03 2024
--- u4.O	Mon Nov 18 23:30:03 2024
***************
*** 1 ****
! 0
\ No newline at end of file
--- 1 ----
! \u0030
\ No newline at end of file
U8...
printf: test U8: stdout mismatch, comparing U8.1 (expected) and U8.O (actual)
*** U8.1	Mon Nov 18 23:30:03 2024
--- U8.O	Mon Nov 18 23:30:03 2024
***************
*** 1 ****
! 0
\ No newline at end of file
--- 1 ----
! \u0030
\ No newline at end of file

[Message part 3 (message/rfc822, inline)]

From: Pádraig Brady <P <at> draigBrady.com>
To: Bruno Haible <bruno <at> clisp.org>, bug-gnulib <at> gnu.org
Cc: 74428-done <at> debbugs.gnu.org, Grisha Levit <grishalevit <at> gmail.com>
Subject: Re: bug#74428: tests/printf/printf-cov failure on macOS
Date: Tue, 19 Nov 2024 18:31:31 +0000

[Message part 4 (text/plain, inline)]

On 19/11/2024 17:34, Bruno Haible wrote:
> Pádraig Brady wrote:
>> I would prefer to bypass the ASCII case if CODE >= 0 && CODE < 128.
>> However is that generally correct?
> 
> Yes, at least for CODE >= 32 && CODE < 128 it is correct.
> This can be seen from the list of supported locale encodings in
> gnulib/lib/localcharset.h.

OK I've adjusted our test to use \u00032 instead,
and tested the attached code, which I'll push later.

thanks,
Pádraig

[gnulib-uc-ascii.diff (text/x-patch, attachment)]

Previous Next

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