GNU bug report logs - #61159
3 test failures

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Jim Meyering <jim <at> meyering.net>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#61159: closed (3 test failures)
Date: Mon, 30 Jan 2023 01:43:02 +0000

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

Your message dated Sun, 29 Jan 2023 17:42:21 -0800
with message-id <CA+8g5KFVd3NJa-xMEBguBX5XYSqt6-HSzo2brxvYcE9qd-X5cw <at> mail.gmail.com>
and subject line Re: bug#61159: 3 test failures
has caused the debbugs.gnu.org bug report #61159,
regarding 3 test failures
to be marked as done.

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


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

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

From: Bruno Haible <bruno <at> clisp.org>
To: bug-sed <at> gnu.org
Subject: 3 test failures
Date: Mon, 30 Jan 2023 01:11:48 +0100

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

Hi Jim,

On Ubuntu Linux/x86_64, after building the current sed git repo
with the current Gnulib, I get 3 test failures:

FAIL: testsuite/compile-errors
FAIL: testsuite/mb-y-translate
FAIL: testsuite/normalize-text

All three are consequences of the commit on 2023-01-02
"maint: reword to avoid a too-long-line warning".

To catch such failures sooner, should I set up a continuous integration
that does a "make check" once every week? (I have such CIs already for
Gnulib, gettext, and a couple of other projects. It's cheap to maintain.)

Bruno

[test-suite.log (text/x-log, attachment)]

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

From: Jim Meyering <jim <at> meyering.net>
To: Bruno Haible <bruno <at> clisp.org>
Cc: 61159-done <at> debbugs.gnu.org
Subject: Re: bug#61159: 3 test failures
Date: Sun, 29 Jan 2023 17:42:21 -0800

On Sun, Jan 29, 2023 at 4:13 PM Bruno Haible <bruno <at> clisp.org> wrote:
> On Ubuntu Linux/x86_64, after building the current sed git repo
> with the current Gnulib, I get 3 test failures:
>
> FAIL: testsuite/compile-errors
> FAIL: testsuite/mb-y-translate
> FAIL: testsuite/normalize-text
>
> All three are consequences of the commit on 2023-01-02
> "maint: reword to avoid a too-long-line warning".

Thanks for catching this. I've just pushed a fix.

> To catch such failures sooner, should I set up a continuous integration
> that does a "make check" once every week? (I have such CIs already for
> Gnulib, gettext, and a couple of other projects. It's cheap to maintain.)

Yes, please. Thanks!

Previous Next

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