From: Phillip Wood <phillip.wood123@gmail.com>
To: Jacob Abel <jacobabel@nullpo.dev>, git@vger.kernel.org
Subject: Re: [PATCH] t2400: Fix test failures when using grep 2.5
Date: Sat, 15 Jul 2023 09:59:23 +0100 [thread overview]
Message-ID: <2e22a23f-576f-7a42-ace8-624a5362d9f4@gmail.com> (raw)
In-Reply-To: <20230715025512.7574-1-jacobabel@nullpo.dev>
Hi Jocab
On 15/07/2023 03:55, Jacob Abel wrote:
> Replace all cases of `\s` with `[[:space:]]` as older versions of GNU
> grep (and from what it seems most versions of BSD grep) do not handle
> `\s`.
>
> For the same reason all cases of `\S` are replaced with `[^[:space:]]`.
> Replacing `\S` also needs to occur as `\S` is technically PCRE and not
> part of ERE even though most modern versions of grep accept it as ERE.
Thanks for working on this fix. Having looked at the changes I think it
would be better just be using a space character in a lot of these
expressions - see below.
> Signed-off-by: Jacob Abel <jacobabel@nullpo.dev>
> ---
> This patch is in response to build failures on GGG's Cirrus CI
> freebsd_12 build jobs[1] and was prompted by a discussion thread [2].
>
> These failures seem to be caused by the behavior outlined in [3].
> Weirdly however they only seem to occur on the FreeBSD CI but not the
> Mac OS CI for some reason despite Mac OS using FreeBSD grep.
>
> 1. https://github.com/gitgitgadget/git/pull/1550/checks?check_run_id=14949695859
> 2. https://lore.kernel.org/git/CALnO6CDryTsguLshcQxx97ZxyY42Twu2hC2y1bLOsS-9zbqXMA@mail.gmail.com/
> 3. https://stackoverflow.com/questions/4233159/grep-regex-whitespace-behavior
>
> t/t2400-worktree-add.sh | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/t/t2400-worktree-add.sh b/t/t2400-worktree-add.sh
> index 0ac468e69e..7f19bdabff 100755
> --- a/t/t2400-worktree-add.sh
> +++ b/t/t2400-worktree-add.sh
> @@ -417,9 +417,9 @@ test_wt_add_orphan_hint () {
> grep "hint: If you meant to create a worktree containing a new orphan branch" actual &&
> if [ $use_branch -eq 1 ]
> then
> - grep -E "^hint:\s+git worktree add --orphan -b \S+ \S+\s*$" actual
> + grep -E "^hint:[[:space:]]+git worktree add --orphan -b [^[:space:]]+ [^[:space:]]+[[:space:]]*$" actual
We know that "hint:" is followed by a single space and all we're really
interested in is that we print something after the "-b " so we can
simplify this to
grep "^hint: git worktree add --orphan -b [^ ]"
I think the same applies to most of the other expressions changed in
this patch.
> else
> - grep -E "^hint:\s+git worktree add --orphan \S+\s*$" actual
> + grep -E "^hint:[[:space:]]+git worktree add --orphan [^[:space:]]+[[:space:]]*$" actual
> fi
>
> '
> @@ -709,7 +709,7 @@ test_dwim_orphan () {
> local info_text="No possible source branch, inferring '--orphan'" &&
> local fetch_error_text="fatal: No local or remote refs exist despite at least one remote" &&
> local orphan_hint="hint: If you meant to create a worktree containing a new orphan branch" &&
> - local invalid_ref_regex="^fatal: invalid reference:\s\+.*" &&
> + local invalid_ref_regex="^fatal: invalid reference:[[:space:]]\+.*" &&
> local bad_combo_regex="^fatal: '[a-z-]\+' and '[a-z-]\+' cannot be used together" &&
>
> local git_ns="repo" &&
> @@ -998,8 +998,8 @@ test_dwim_orphan () {
> headpath=$(git $dashc_args rev-parse --sq --path-format=absolute --git-path HEAD) &&
I'm a bit confused by the --sq here - why does it need to be shell
quoted when it is always used inside double quotes? Also when the
reftable backend is used I'm not sure that HEAD is actually a file in
$GIT_DIR anymore (that's less of an issue at the moment as that backend
is not is use yet).
> headcontents=$(cat "$headpath") &&
> grep "HEAD points to an invalid (or orphaned) reference" actual &&
> - grep "HEAD path:\s*.$headpath." actual &&
> - grep "HEAD contents:\s*.$headcontents." actual &&
> + grep "HEAD path:[[:space:]]*.$headpath." actual &&
> + grep "HEAD contents:[[:space:]]*.$headcontents." actual &&
Using grep like this makes it harder to debug test failures as one has
to run the test with "-x" in order to try and figure out which grep
actually failed. I think here we can replace the sequence of "grep"s
with "test_cmp"
cat >expect <<-EOF &&
HEAD points to an invalid (or orphaned) reference
HEAD path: $headpath
HEAD contents: $headcontents
EOF
test_cmp expect actual
Best Wishes
Phillip
> grep "$orphan_hint" actual &&
> ! grep "$info_text" actual
> fi &&
>
> base-commit: 830b4a04c45bf0a6db26defe02ed1f490acd18ee
next prev parent reply other threads:[~2023-07-15 8:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 2:55 [PATCH] t2400: Fix test failures when using grep 2.5 Jacob Abel
2023-07-15 8:59 ` Phillip Wood [this message]
2023-07-15 23:15 ` Jacob Abel
2023-07-16 1:08 ` Junio C Hamano
2023-07-16 2:55 ` Jacob Abel
2023-07-16 15:34 ` Phillip Wood
2023-07-17 2:38 ` Junio C Hamano
2023-07-18 0:44 ` Jacob Abel
2023-07-18 13:36 ` Phillip Wood
2023-07-21 4:35 ` Jacob Abel
2023-07-15 23:36 ` Jacob Abel
2023-07-16 3:38 ` [PATCH v2] " Jacob Abel
2023-07-21 4:40 ` [PATCH v3 0/3] " Jacob Abel
2023-07-21 4:40 ` [PATCH v3 1/3] t2400: drop no-op `--sq` from rev-parse call Jacob Abel
2023-07-21 4:40 ` [PATCH v3 2/3] builtin/worktree.c: convert tab in advice to space Jacob Abel
2023-07-21 4:40 ` [PATCH v3 3/3] t2400: rewrite regex to avoid unintentional PCRE Jacob Abel
2023-07-21 15:16 ` Junio C Hamano
2023-07-21 15:49 ` Junio C Hamano
2023-07-22 2:36 ` Jacob Abel
2023-07-26 21:42 ` [PATCH v4 0/3] t2400: Fix test failures when using grep 2.5 Jacob Abel
2023-07-26 21:42 ` [PATCH v4 1/3] t2400: drop no-op `--sq` from rev-parse call Jacob Abel
2023-07-26 21:42 ` [PATCH v4 2/3] builtin/worktree.c: convert tab in advice to space Jacob Abel
2023-07-26 21:42 ` [PATCH v4 3/3] t2400: rewrite regex to avoid unintentional PCRE Jacob Abel
2023-07-26 22:09 ` [PATCH v4 0/3] t2400: Fix test failures when using grep 2.5 Junio C Hamano
2023-07-28 13:09 ` Phillip Wood
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=2e22a23f-576f-7a42-ace8-624a5362d9f4@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=jacobabel@nullpo.dev \
--cc=phillip.wood@dunelm.org.uk \
/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).