From: "Torsten Bögershausen" <tboegi@web.de>
To: "A. Wilcox" <awilfox@adelielinux.org>, git@vger.kernel.org
Subject: Re: Test failures when Git is built with libpcre and grep is built without it
Date: Sun, 1 Jan 2017 11:19:51 +0100 [thread overview]
Message-ID: <38525b2e-2a5f-941f-2eca-912632f9a2ec@web.de> (raw)
In-Reply-To: <58688C9F.4000605@adelielinux.org>
On 01.01.17 05:59, A. Wilcox wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hello!
>
> I'm attempting to package Git for our new Linux distribution and I
> have run in to a failure on our PowerPC builder while running the test
> suite.
>
> The PowerPC builder runs a tiny version of grep(1) that was not built
> with PCRE. As such, grep -P returns 2 and prints:
>
> grep: support for the -P option is not compiled into this
> - --disable-perl-regexp binary
>
> However, our Git build *does* link against libpcre. This causes a
> tests numbered 142 and 143 to fail in t7810-grep.sh.
>
> I am not sure the best way to handle this but I felt it would be
> prudent to inform you of this issue. I will be happy to provide any
> other information you may require.
The first thing you can do is to run the test with debug and verbose:
debug=t verbose=t ./t7810-grep.sh
and post the output of these 2 test cases here:
(mine looks like this)
expecting success:
echo "ab:a+bc" >expected &&
git \
-c grep.patterntype=extended \
-c grep.patterntype=fixed \
-c grep.patterntype=basic \
grep "a+b*c" ab >actual &&
test_cmp expected actual
ok 142 - grep pattern with grep.patternType=extended, =fixed, =basic
expecting success:
echo "ab:abc" >expected &&
git grep -F -G -E "a+b*c" ab >actual &&
test_cmp expected actual
ok 143 - grep -F -G -E pattern
next prev parent reply other threads:[~2017-01-01 10:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 4:59 Test failures when Git is built with libpcre and grep is built without it A. Wilcox
2017-01-01 10:19 ` Torsten Bögershausen [this message]
2017-01-02 6:53 ` Jeff King
2017-01-09 10:51 ` A. Wilcox
2017-01-09 11:27 ` Jeff King
2017-01-09 13:05 ` Andreas Schwab
2017-01-09 21:33 ` Jeff King
2017-01-10 10:36 ` A. Wilcox
2017-01-10 11:40 ` [musl] " Szabolcs Nagy
2017-01-11 10:04 ` Jeff King
2017-01-11 11:10 ` [PATCH] t7810: avoid assumption about invalid regex syntax Jeff King
2017-01-11 20:49 ` [musl] Re: Test failures when Git is built with libpcre and grep is built without it Junio C Hamano
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38525b2e-2a5f-941f-2eca-912632f9a2ec@web.de \
--to=tboegi@web.de \
--cc=awilfox@adelielinux.org \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).