list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: "Amanda  Shafack  via GitGitGadget" <>
Cc: Emily Shaffer <>,
	Jonathan Nieder <>,
	Amanda Shafack <>
Subject: [PATCH 0/2] [Outreachy][Patch v1] t9832,t2200: avoid using pipes in git related commands
Date: Sat, 17 Oct 2020 16:02:30 +0000
Message-ID: <> (raw)

When the upstream of a pipe throws an error, the downstream still executes
normally. This happens because the exit code of the upstream in a pipe is
ignored. This behavior can make debugging very hard in case a test fails.
Also, pipes are prone to deadlocks. If the upstream gets full, the commands
downstream will never start.

Write out the output of the git command to a file, so as to test the exit
codes of both commands.

Commit c6f44e1da5 (t9813: avoid using pipes, 2017-01-04) noticed that the
exit code of upstream in the pipe is ignored, thus using pipes should be

Signed-off-by: Amanda Shafack

Amanda  Shafack (1):
  t2200: modify code syntax

Amanda Shafack (1):
  t9832,t2200: avoid using pipes in git commands

 t/ | 3 ++-
 t/   | 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

base-commit: a5fa49ff0a8f3252c6bff49f92b85e7683868f8a
Fetch-It-Via: git fetch pr-git-885/lkmandy/avoid-pipes-v1

             reply	other threads:[~2020-10-17 16:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-17 16:02 Amanda  Shafack  via GitGitGadget [this message]
2020-10-17 16:02 ` [PATCH 1/2] t9832,t2200: avoid using pipes in git commands Amanda Shafack via GitGitGadget
2020-10-18  6:11   ` Eric Sunshine
2020-10-18 13:57     ` Amanda Shafack
2020-10-17 16:02 ` [PATCH 2/2] t2200: modify code syntax Amanda  Shafack via GitGitGadget
2020-10-18  5:55   ` Eric Sunshine
2020-10-18 13:59     ` Amanda Shafack
2020-10-18 14:42 ` [PATCH v2] t9832,t2200: avoid using pipes in git commands Amanda  Shafack  via GitGitGadget
2020-10-18 19:25   ` Eric Sunshine
2020-10-18 20:04     ` Junio C Hamano
2020-10-18 22:04       ` Amanda Shafack
2020-10-18 20:40     ` Amanda Shafack
2020-10-18 20:48   ` [PATCH v3] t2200,t9832: avoid using 'git' upstream in a pipe Amanda  Shafack  via GitGitGadget
2020-10-18 21:01     ` 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ \
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

code repositories for the project(s) associated with this inbox:

AGPL code for this site: git clone