grep-devel
[Top][All Lists]
Advanced

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

Re: [Grep-devel] [platform-testers] new snapshot available: grep-3.1.51-


From: Bruce Dubbs
Subject: Re: [Grep-devel] [platform-testers] new snapshot available: grep-3.1.51-e767
Date: Wed, 19 Dec 2018 15:13:08 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0

On 12/19/2018 11:11 AM, Jim Meyering wrote:
On Tue, Dec 18, 2018 at 9:13 AM Jose E. Marchesi <address@hidden> wrote:
In Oracle Linux 6.9 on a SPARC S7 (sparc64):

pcre: skipped test: no PCRE support
SKIP: pcre
pcre-abort: skipped test: no PCRE support
...

I had to manually skip mb-non-UTF8-performance because the `times' perl
command in this system always returns 0 for all four times, so the while
loop in the test driver never finishes (ugh).

Ugh. Which version of perl is that? I.e., what does perl -V print?
After the release, I'll consider adding a require_perl_times_ function
that will cause that test to be skipped on such systems.

For LFS, we do not build grep with PCRE by default. Users are free to rebuild after pcre-8.42 is installed in BLFS.

On my system (x86_64, linux-4.19.8, glibc-2,28, gcc-8.2) with pcre installed I have )for grep-3.1):

XFAIL: triple-backref
XPASS: backref-alt

SKIP: big-hole
SKIP: big-match
SKIP: false-match-mb-non-utf8
SKIP: long-line-vs-2GiB-read
SKIP: long-pattern-perf
SKIP: mb-non-UTF8-performance
SKIP: sjis-mb

SKIP: test-vc-list-files-git.sh
SKIP: test-vc-list-files-cvs.sh
SKIP: test-wcrtomb-w32-1.sh
SKIP: test-wcrtomb-w32-2.sh
SKIP: test-wcrtomb-w32-3.sh
SKIP: test-wcrtomb-w32-4.sh
SKIP: test-wcrtomb-w32-5.sh

If I run with RUN_EXPENSIVE_TESTS=yes, I get

false-match-mb-non-utf8: skipped test: no support for the zh_HK.big5hkscs locale
 warning: \s failed to match \x0a in the en_US.UTF-8 locale
 warning: \s failed to match \x85 in the en_US.UTF-8 locale
 warning: \s failed to match \xc2\xa0 in the en_US.UTF-8 locale
 warning: \S mistakenly matched \xc2\xa0 in the en_US.UTF-8 locale
 warning: \s failed to match \xe2\x80\x87 in the en_US.UTF-8 locale
 warning: \S mistakenly matched \xe2\x80\x87 in the en_US.UTF-8 locale
 warning: \s failed to match \xe2\x80\x8b in the en_US.UTF-8 locale
 warning: \S mistakenly matched \xe2\x80\x8b in the en_US.UTF-8 locale
 warning: \s failed to match \xe2\x80\xaf in the en_US.UTF-8 locale
 warning: \S mistakenly matched \xe2\x80\xaf in the en_US.UTF-8 locale
sjis-mb: skipped test: SJIS locale not found

with only
SKIP: false-match-mb-non-utf8
SKIP: sjis-mb
------------------------------
For grep-3.1.51-e767:
No failures. 15 SKIP, 2 XFAIL

XFAIL: equiv-classes
XFAIL: triple-backref

SKIP: big-hole
SKIP: big-match
SKIP: false-match-mb-non-utf8
SKIP: long-line-vs-2GiB-read
SKIP: long-pattern-perf
SKIP: mb-non-UTF8-performance
SKIP: sjis-mb

SKIP: test-c-stack2.sh
SKIP: test-vc-list-files-git.sh
SKIP: test-vc-list-files-cvs.sh
SKIP: test-wcrtomb-w32-1.sh
SKIP: test-wcrtomb-w32-2.sh
SKIP: test-wcrtomb-w32-3.sh
SKIP: test-wcrtomb-w32-4.sh
SKIP: test-wcrtomb-w32-5.sh

Expensive tests:

SKIP: false-match-mb-non-utf8
SKIP: sjis-mb

SKIP: test-c-stack2.sh
SKIP: test-vc-list-files-git.sh
SKIP: test-vc-list-files-cvs.sh
SKIP: test-wcrtomb-w32-1.sh
SKIP: test-wcrtomb-w32-2.sh
SKIP: test-wcrtomb-w32-3.sh
SKIP: test-wcrtomb-w32-4.sh
SKIP: test-wcrtomb-w32-5.sh

XFAIL: equiv-classes
XFAIL: triple-backref

Also:

address@hidden build]$ i=200; printf %0${i}0000d 0|tr 0 '(' > in; src/grep -Ef 
in; echo $?
grep: stack overflow
2

For this I get in 3.1:

# i=200; printf %0${i}0000d 0|tr 0 '(' > in; src/grep -Ef in; echo $?
Segmentation fault

For 3.1.51-e767

# i=200; printf %0${i}0000d 0|tr 0 '(' > in; src/grep -Ef in; echo $?
grep: stack overflow
2

  -- Bruce Dubbs
     linuxfromscratch.org

Hi Jose,
Thanks for testing on those less-common systems and for reporting the results.
I guess you know that you can avoid those skipped tests if you first
install libpcre.

Without PCRE, grep's -P option does not work. I've become so dependent
on that (for command-line use at least), I would never accept its
absence on any system I use :-)






reply via email to

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