From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>,
Andrei Rybak <rybak.a.v@gmail.com>
Cc: git@vger.kernel.org, Denton Liu <liu.denton@gmail.com>
Subject: Re: [PATCH] test: rev-parse-upstream: add missing cmp
Date: Tue, 09 May 2023 20:56:31 -0700 [thread overview]
Message-ID: <xmqqpm78zvo0.fsf@gitster.g> (raw)
In-Reply-To: 20230509000246.1760327-1-felipe.contreras@gmail.com
Felipe Contreras <felipe.contreras@gmail.com> writes:
> It seems pretty clear 5236fce6b4 (t1507: stop losing return codes of git
> commands, 2019-12-20) missed a test_cmp.
>
> Cc: Denton Liu <liu.denton@gmail.com>
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> ---
> t/t1507-rev-parse-upstream.sh | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/t/t1507-rev-parse-upstream.sh b/t/t1507-rev-parse-upstream.sh
> index d94c72c672..cb9ef7e329 100755
> --- a/t/t1507-rev-parse-upstream.sh
> +++ b/t/t1507-rev-parse-upstream.sh
> @@ -97,7 +97,8 @@ test_expect_success 'my-side@{u} resolves to correct commit' '
> commit_subject my-side >actual &&
> test_cmp expect actual &&
> echo 5 >expect &&
> - commit_subject my-side@{u} >actual
> + commit_subject my-side@{u} >actual &&
> + test_cmp expect actual
> '
>
> test_expect_success 'not-tracking@{u} fails' '
Good eyes.
a93cbe8d (t1507: assert output of rev-parse, 2023-03-18) and wanted
to do the same to this script, and the series that contains the
commit wanted to do the same to many other test scripts, but it
seems to have missed this one.
Will queue (on top of a93cbe8d, naturally).
Thanks.
prev parent reply other threads:[~2023-05-10 4:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 0:02 [PATCH] test: rev-parse-upstream: add missing cmp Felipe Contreras
2023-05-10 3:56 ` 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=xmqqpm78zvo0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=liu.denton@gmail.com \
--cc=rybak.a.v@gmail.com \
/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).