GNU bug report logs - #63533
test-mbrlen5.sh failure

Previous Next

Full log

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

From: Carlo Marcelo Arenas Belón <carenas <at> gmail.com>
To: Jim Meyering <jim <at> meyering.net>
Cc: Caleb Zulawski <caleb.zulawski <at> gmail.com>, 63533 <at> debbugs.gnu.org
Subject: Re: bug#63533: test-mbrlen5.sh failure
Date: Fri, 19 May 2023 12:43:17 -0700

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

On Thu, May 18, 2023 at 10:09:38PM +0200, Jim Meyering wrote:
> On Thu, May 18, 2023 at 2:44 PM Carlo Marcelo Arenas Belón
> <carenas <at> gmail.com> wrote:
> > On Wed, May 17, 2023 at 09:09:02PM -0400, Caleb Zulawski wrote:
> > >
> > > Isn’t this test too strict, then?
> >
> > It shouldn't had been included with the release; the attached patch
> > should help with that for future releases.
> 
> Thanks for looking into this, Carlo.
> 
> However, I think we should not limit the gnulib tests that are run via
> grep just to accommodate systems with broken code, even when grep
> happens not to exercise the broken code path.

Make a good point, specially considering that it should only affect systems
that are EOL like Centos 7, Debian 9 or Ubuntu 16.04 (although some of those
might be still supported) and that would be also likely to fail for other
reasons (ex: not being Y2K38 safe).

I think though, for consistency, the attached should be applied instead.  A
snapshot build with it shows 3 failing gnulib tests when tested in
gcc45.fsffrance.org.

Carlo

[0001-gnulib-allow-mbrtowc-tests.patch (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.