bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Jeffrey Walton <noloader@gmail.com>,
	"bug-gnulib@gnu.org List" <bug-gnulib@gnu.org>
Cc: platform-testers@gnu.org, GNU grep developers <grep-devel@gnu.org>
Subject: Re: [platform-testers] new snapshot available: grep-3.4-almost.19-ff30
Date: Thu, 17 Sep 2020 07:40:18 -0700	[thread overview]
Message-ID: <CA+8g5KHeM4Z6FQgZR-QBPFD+fZo5Z0v3mKL4BMa0-8101Mqfpg@mail.gmail.com> (raw)
In-Reply-To: <CAH8yC8mn1YMN+fgzJBKEk9+y0qTqfO2zHbWUyO2ekVq-PimX3Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 702 bytes --]

On Thu, Sep 17, 2020 at 6:37 AM Jeffrey Walton <noloader@gmail.com> wrote:
> Hi Everyone,
>
> grep-3.4-almost.19-ff30 fails self test on Alpine Linux 3.10 with
> BusyBox, triplet x86_64-pc-linux-gnu.
>
>   FAIL: test-dfa-match.sh

Thank you for reporting that. I'll start with that first issue.
That is due to a now-erroneous test for busybox-specific timeout
program which used to require "-t" before the timeout value.
Now, it has aligned with coreutils, since the 31 December 2018 release
of BusyBox 1.30.0 (unstable).
I've fixed it with the attached patch, also just pushed to gnulib.

>   FAIL: test-hard-locale
>   FAIL: test-setlocale_null-mt-all
>
> Attached are config.log and test-suite.log.

[-- Attachment #2: test-dfa-match.sh--busybox-vs-timeout.patch --]
[-- Type: application/octet-stream, Size: 1461 bytes --]

From d7d69621581065274582c78981b58dbce4313d2c Mon Sep 17 00:00:00 2001
From: Jim Meyering <meyering@fb.com>
Date: Thu, 17 Sep 2020 07:36:26 -0700
Subject: [PATCH] test-dfa-match.sh: port timeout work-around to newer Busybox

* tests/test-dfa-match.sh: Update timeout -t portability test to
accommodate Busybox 1.30.0 and newer.
---
 ChangeLog               | 6 ++++++
 tests/test-dfa-match.sh | 4 +++-
 2 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/ChangeLog b/ChangeLog
index bbd420cb2..e5b50bf55 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2020-09-17  Jim Meyering  <meyering@fb.com>
+
+	test-dfa-match.sh: port timeout work-around to newer Busybox
+	* tests/test-dfa-match.sh: Update timeout -t portability test to
+	accommodate Busybox 1.30.0 and newer.
+
 2020-09-16  Paul Eggert  <eggert@cs.ucla.edu>

 	fnmatch: adjust to match glibc fix
diff --git a/tests/test-dfa-match.sh b/tests/test-dfa-match.sh
index a7285ec0b..d3c434d66 100755
--- a/tests/test-dfa-match.sh
+++ b/tests/test-dfa-match.sh
@@ -22,7 +22,9 @@
 path_prepend_ .

 if (type timeout) >/dev/null 2>&1; then
-  if timeout --help 2>&1 | grep BusyBox; then
+    # Busybox's timeout required -t until its 1.30.0 release on 2018-12-31,
+    # after which it became compatible with coreutils' timeout.
+  if timeout --help 2>&1 | grep BusyBox && timeout -t 0 true; then
     timeout_10='timeout -t 10'
   else
     timeout_10='timeout 10'
-- 
2.28.0.394.ge197136389


       reply	other threads:[~2020-09-17 14:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2imce1gpu.fsf@meyering.net>
     [not found] ` <CAH8yC8mn1YMN+fgzJBKEk9+y0qTqfO2zHbWUyO2ekVq-PimX3Q@mail.gmail.com>
2020-09-17 14:40   ` Jim Meyering [this message]
2020-09-17 22:46   ` [platform-testers] new snapshot available: grep-3.4-almost.19-ff30 Bruno Haible
2020-09-19 13:12   ` Bruno Haible
2020-09-19 14:21     ` Jeffrey Walton
2020-09-19 19:15       ` Bruno Haible
2020-09-20 19:28     ` Bruno Haible
     [not found] ` <CAH8yC8n4tmO6__C=zP0JZRmc5_ddg7L6uGAuLfjV_Bm+i3oYsA@mail.gmail.com>
2020-09-17 18:23   ` Paul Eggert
2020-09-17 20:53 ` grep-3.4-almost.19-ff30 on Solaris 10 Bruno Haible
2020-09-18  2:26   ` Paul Eggert
2020-09-18  9:01     ` Bruno Haible
2020-09-18 16:06       ` Paul Eggert
2020-09-19  0:25         ` gl_SILENT Bruno Haible
2020-09-17 21:07 ` [platform-testers] new snapshot available: grep-3.4-almost.19-ff30 Jeffrey Walton
2020-09-18 17:36   ` Paul Eggert
     [not found] <CMM.0.95.0.1600356616.beebe@gamma.math.utah.edu>
2020-09-17 19:22 ` Paul Eggert
2020-09-17 21:31 ` Paul Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+8g5KHeM4Z6FQgZR-QBPFD+fZo5Z0v3mKL4BMa0-8101Mqfpg@mail.gmail.com \
    --to=jim@meyering.net \
    --cc=bug-gnulib@gnu.org \
    --cc=grep-devel@gnu.org \
    --cc=noloader@gmail.com \
    --cc=platform-testers@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).