git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ayush Chandekar <ayu.chandekar@gmail.com>
Cc: git@vger.kernel.org,  sunshine@sunshineco.com
Subject: Re: [GSOC][PATCH v2] t6422: avoid suppressing Git’s exit code in tests
Date: Wed, 05 Feb 2025 12:47:43 -0800	[thread overview]
Message-ID: <xmqqh658m840.fsf@gitster.g> (raw)
In-Reply-To: <20250205142817.42117-1-ayu.chandekar@gmail.com> (Ayush Chandekar's message of "Wed, 5 Feb 2025 19:58:17 +0530")

Ayush Chandekar <ayu.chandekar@gmail.com> writes:

Thanks for practicing yet another iteration.  I am not going to
actually replace the previous one with this one, as the previous one
is just OK, but let's pretend I would to complete the "simulated"
iteration.

Below, pretend that we will discard the previous one and replace it
with this one, and plan to merge the result to 'next', but that is
only for practice.

---

> Subject: Re: [GSOC][PATCH v2] t6422: avoid suppressing Git’s exit code in tests

This is about 6423 ;-)  I'll amend while applying the patch.

> Some test in t6423 supress Git's exit code, which can cause test
> failures go unnoticed. Specifically using git <subcommand> |
> <other-command> masks potential failures of the Git command.
>
> Instead of executing a Git command as the upstream component of
> a pipe, which can result in the exit status being lost, redirect
> its output to a file and then process that file in two steps to
> ensure the exit status is properly preserved.
>
> Signed-off-by: Ayush Chandekar <ayu.chandekar@gmail.com>
> ---
>  t/t6423-merge-rename-directories.sh | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)

OK.  And the change to the test body to lose input redirection into
"uniq" look OK, too.

Thanks.  Let's replace it and mark the topic for 'next'.


  reply	other threads:[~2025-02-05 20:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-02 12:09 [PATCH] t6423: fix suppression of Git’s exit code in tests ayu-ch
2025-02-02 13:18 ` Meet Soni
2025-02-02 13:35 ` Eric Sunshine
2025-02-03  0:04   ` Junio C Hamano
2025-02-04  0:38     ` Ayush Chandekar
2025-02-04 13:08       ` Junio C Hamano
2025-02-05 14:28         ` [GSOC][PATCH v2] t6422: avoid suppressing " Ayush Chandekar
2025-02-05 20:47           ` Junio C Hamano [this message]
2025-02-06  5:08             ` [GSOC][PATCH v2] t6423: " Ayush Chandekar

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=xmqqh658m840.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ayu.chandekar@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sunshine@sunshineco.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).