From: Junio C Hamano <gitster@pobox.com>
To: Shlok Kulshreshtha <diy2903@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] t7614: avoid hiding git's exit code in a pipe
Date: Wed, 15 Jul 2026 12:36:29 -0700 [thread overview]
Message-ID: <xmqq1pd4m4ea.fsf@gitster.g> (raw)
In-Reply-To: <20260715113344.3490-1-diy2903@gmail.com> (Shlok Kulshreshtha's message of "Wed, 15 Jul 2026 17:03:44 +0530")
Shlok Kulshreshtha <diy2903@gmail.com> writes:
> The exit code of the upstream command in a pipe is ignored, so in
>
> git cat-file commit HEAD | sed -e "1,/^\$/d" >actual
>
> a crash of "git cat-file" would go unnoticed: the exit code of the
> pipeline is that of "sed", which happily succeeds on empty input. The
> test would thus pass even though "git cat-file" failed.
>
> Write the output of "git cat-file" to a file first and run "sed" on
> that file, so that the exit codes of both commands are checked by the
> &&-chain.
>
> Signed-off-by: Shlok Kulshreshtha <diy2903@gmail.com>
> ---
> This is a microproject ("Avoid suppressing git's exit code in test
> scripts"), applying the same fix as c6f44e1da5 (t9813: avoid using
> pipes) to another script. A search of the list did not turn up anyone
> working on t7614; please let me know if it is already taken.
All look trivially correct.
Two clean-up possibilities that are clearly outside the scope of
this patch are
* There is no need to backslash-quote the dollar sign.
t7604-merge-custom-message.sh next door uses "1,/^$/d" just fine.
* This "cat-file the commit object, and strip away the object
header with sed" pattern appears quite often throughout the test
suite.
$ git grep -B1 -e 'sed -e "1,/^\\*$/d"' t/
shows quite a few hits. It might make sense to give them an easy
to use helper script
commit_body () {
git cat-file commit "$1" >.commit &&
sed -e "1,/^$/d" .commit &&
rm -f .commit
}
or something like that.
But again, these are clearly outside the scope of this patch.
>
> t/t7614-merge-signoff.sh | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/t/t7614-merge-signoff.sh b/t/t7614-merge-signoff.sh
> index fee258d4f0..e58bf07b7a 100755
> --- a/t/t7614-merge-signoff.sh
> +++ b/t/t7614-merge-signoff.sh
> @@ -45,7 +45,8 @@ test_expect_success 'git merge --signoff adds a sign-off line' '
> test_commit main-branch-2 file2 2 &&
> git checkout other-branch &&
> git merge main --signoff --no-edit &&
> - git cat-file commit HEAD | sed -e "1,/^\$/d" >actual &&
> + git cat-file commit HEAD >commit &&
> + sed -e "1,/^\$/d" commit >actual &&
> test_cmp expected-signed actual
> '
>
> @@ -55,7 +56,8 @@ test_expect_success 'git merge does not add a sign-off line' '
> test_commit main-branch-3 file3 3 &&
> git checkout other-branch &&
> git merge main --no-edit &&
> - git cat-file commit HEAD | sed -e "1,/^\$/d" >actual &&
> + git cat-file commit HEAD >commit &&
> + sed -e "1,/^\$/d" commit >actual &&
> test_cmp expected-unsigned actual
> '
>
> @@ -65,7 +67,8 @@ test_expect_success 'git merge --no-signoff flag cancels --signoff flag' '
> test_commit main-branch-4 file4 4 &&
> git checkout other-branch &&
> git merge main --no-edit --signoff --no-signoff &&
> - git cat-file commit HEAD | sed -e "1,/^\$/d" >actual &&
> + git cat-file commit HEAD >commit &&
> + sed -e "1,/^\$/d" commit >actual &&
> test_cmp expected-unsigned actual
> '
prev parent reply other threads:[~2026-07-15 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 11:33 [PATCH] t7614: avoid hiding git's exit code in a pipe Shlok Kulshreshtha
2026-07-15 19:36 ` Junio C Hamano [this message]
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=xmqq1pd4m4ea.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=diy2903@gmail.com \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox