From: Andreas Schwab <schwab@linux-m68k.org>
To: "A. Wilcox" <awilfox@adelielinux.org>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Test failures when Git is built with libpcre and grep is built without it
Date: Mon, 09 Jan 2017 14:05:44 +0100 [thread overview]
Message-ID: <871swcjsd3.fsf@linux-m68k.org> (raw)
In-Reply-To: <58736B2A.40003@adelielinux.org> (A. Wilcox's message of "Mon, 9 Jan 2017 04:51:22 -0600")
On Jan 09 2017, "A. Wilcox" <awilfox@adelielinux.org> wrote:
> Interestingly enough, you seem to be right. The failure is very
> bizarre and has nothing to do with system /bin/grep:
>
> test_must_fail: command succeeded: git grep -G -F -P -E a\x{2b}b\x{2a}c ab
> not ok 142 - grep -G -F -P -E pattern
> #
> # >empty &&
> # test_must_fail git grep -G -F -P -E "a\x{2b}b\x{2a}c"
> ab >actual &&
> # test_cmp empty actual
> #
>
> However:
>
> elaine trash directory.t7810-grep # git grep -G -F -P -E
> a\x{2b}b\x{2a}c ab >actual
You need to quote the regexp argument, see the line starting with
"test_must_fail" above.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-01-09 13:06 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871swcjsd3.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=awilfox@adelielinux.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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 NNTP newsgroup(s).