GNU bug report logs - #61159
3 test failures

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 61159 in the body.
You can then email your comments to 61159 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

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 1 (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 #8 received at 61159 <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: Bruno Haible <bruno <at> clisp.org>
Cc: 61159 <at> debbugs.gnu.org
Subject: Re: bug#61159: 3 test failures
Date: Sun, 29 Jan 2023 17:17:12 -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 fixed it locally.

> 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!

Message #13 received at 61159-done <at> debbugs.gnu.org (full text, mbox):

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.