grep-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

grep branch, master, updated. v3.7-100-gb47a3fb


From: Jim Meyering
Subject: grep branch, master, updated. v3.7-100-gb47a3fb
Date: Sun, 3 Jul 2022 13:22:14 -0400 (EDT)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "grep".

The branch, master has been updated
       via  b47a3fb1554cd7d9d69b9c662e8a91438f30025a (commit)
       via  90bc5d93f167da68b78bc5e0797af1e9dfe17ce0 (commit)
      from  c9ac429ddddd573d75d59b90e2cd1564fbedddbc (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://git.savannah.gnu.org/cgit/grep.git/commit/?id=b47a3fb1554cd7d9d69b9c662e8a91438f30025a


commit b47a3fb1554cd7d9d69b9c662e8a91438f30025a
Author: Jim Meyering <meyering@fb.com>
Date:   Sun Jul 3 10:21:49 2022 -0700

    tests: note that triple-backref is still not fixed
    
    * tests/triple-backref: I noticed that our sole XFAIL is still
    required, in spite of a glibc comment that bug 11053 is fixed,
    so confirmed that it no longer evokes an abort, but still fails
    to produce the expected match.  I.e., this prints nothing:
    echo a | grep -E '(.?)(.?)(.?)\3\2\1' -- it should print its input.

diff --git a/tests/triple-backref b/tests/triple-backref
index 80b6ddc..d9de801 100755
--- a/tests/triple-backref
+++ b/tests/triple-backref
@@ -24,6 +24,7 @@ MALLOC_CHECK_=
 warn_ "$ME_: expect malfunction on glibc systems due to" \
    "https://sourceware.org/bugzilla/show_bug.cgi?id=11053";
 
+# While with glibc-2.35, it no longer aborts, the empty result is still wrong:
 timeout 10 grep -E '(.?)(.?)(.?)\3\2\1' in > out || fail=1
 compare out in || fail=1
 

http://git.savannah.gnu.org/cgit/grep.git/commit/?id=90bc5d93f167da68b78bc5e0797af1e9dfe17ce0


commit b47a3fb1554cd7d9d69b9c662e8a91438f30025a
Author: Jim Meyering <meyering@fb.com>
Date:   Sun Jul 3 10:21:49 2022 -0700

    tests: note that triple-backref is still not fixed
    
    * tests/triple-backref: I noticed that our sole XFAIL is still
    required, in spite of a glibc comment that bug 11053 is fixed,
    so confirmed that it no longer evokes an abort, but still fails
    to produce the expected match.  I.e., this prints nothing:
    echo a | grep -E '(.?)(.?)(.?)\3\2\1' -- it should print its input.

diff --git a/tests/triple-backref b/tests/triple-backref
index 80b6ddc..d9de801 100755
--- a/tests/triple-backref
+++ b/tests/triple-backref
@@ -24,6 +24,7 @@ MALLOC_CHECK_=
 warn_ "$ME_: expect malfunction on glibc systems due to" \
    "https://sourceware.org/bugzilla/show_bug.cgi?id=11053";
 
+# While with glibc-2.35, it no longer aborts, the empty result is still wrong:
 timeout 10 grep -E '(.?)(.?)(.?)\3\2\1' in > out || fail=1
 compare out in || fail=1
 

-----------------------------------------------------------------------

Summary of changes:
 tests/hash-collision-perf | 1 -
 tests/triple-backref      | 1 +
 2 files changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
grep



reply via email to

[Prev in Thread] Current Thread [Next in Thread]