From: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
To: git@vger.kernel.org
Cc: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Subject: [PATCH v2 0/2] t6300: clear warning when running without gpg
Date: Wed, 18 Aug 2021 12:19:25 +0700 [thread overview]
Message-ID: <cover.1629263759.git.congdanhqx@gmail.com> (raw)
In-Reply-To: <bcbde2e7364865ac16702447b863b8a725670428.1629200841.git.congdanhqx@gmail.com>
Running t6300 in an environment without gpg(1),
we'll see those warnings:
fatal: Not a valid object name refs/tags/signed-empty
fatal: Not a valid object name refs/tags/signed-short
fatal: Not a valid object name refs/tags/signed-long
Because, those objects will be created only when GPG is satistified.
This series try to clean those errors.
Change from v1:
* Make 1/2 as near pure-code-move; and
* Use 2/2 as a code change to preserve status code for cat-file
* Mention reasons that 1/2 couldn't be pure-code-move.
Đoàn Trần Công Danh (2):
t6300: don't run cat-file on non-existent object
t6300: check for cat-file exit status code
t/t6300-for-each-ref.sh | 29 ++++++++++++++++++-----------
1 file changed, 18 insertions(+), 11 deletions(-)
Range-diff against v1:
1: 6d36f3a8df ! 1: b813d6f2ad t6300: don't run cat-file on non-existent object
@@ Commit message
* skip their execution if prerequisites aren't satistified.
* check their exit status code
+ The expected value for objects with type: commit needs to be
+ computed outside the test because we can't relies on "$3" there.
+ Furthermore, to prevent the accidental usage of that computed
+ expected value, BUG out on unknown object's type.
+
Signed-off-by: Đoàn Trần Công Danh <congdanhqx@gmail.com>
## t/t6300-for-each-ref.sh ##
@@ t/t6300-for-each-ref.sh: test_atom() {
- esac
- # Leave $expect unquoted to lose possible leading whitespaces
- echo $expect >expected
++ # for commit leg, $3 is changed there
+ expect=$(printf '%s' "$3" | wc -c)
test_expect_${4:-success} $PREREQ "basic atom: $1 contents:size" '
+ type=$(git cat-file -t "$ref") &&
+ case $type in
+ tag)
+ # We cannot use $3 as it expects sanitize_pgp to run
-+ git cat-file tag $ref >out &&
-+ expect=$(<out tail -n +6 | wc -c) ;;
++ expect=$(git cat-file tag $ref | tail -n +6 | wc -c) ;;
+ tree | blob)
+ expect="" ;;
+ commit)
-: ---------- > 2: 68ee769121 t6300: check for cat-file exit status code
--
2.33.0.rc1
next prev parent reply other threads:[~2021-08-18 5:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 11:48 [PATCH] t6300: don't run cat-file on non-existent object Đoàn Trần Công Danh
2021-08-17 21:44 ` Johannes Schindelin
2021-08-18 5:19 ` Đoàn Trần Công Danh [this message]
2021-08-18 5:19 ` [PATCH v2 1/2] " Đoàn Trần Công Danh
2021-08-19 20:16 ` Junio C Hamano
2021-08-18 5:19 ` [PATCH v2 2/2] t6300: check for cat-file exit status code Đoàn Trần Công Danh
2021-08-19 20:19 ` Junio C Hamano
2021-08-18 10:33 ` [PATCH v2 0/2] t6300: clear warning when running without gpg Johannes Schindelin
2021-08-21 1:36 ` [PATCH v3 " Đoàn Trần Công Danh
2021-08-21 1:36 ` [PATCH v3 1/2] t6300: don't run cat-file on non-existent object Đoàn Trần Công Danh
2021-08-21 1:36 ` [PATCH v3 2/2] t6300: check for cat-file exit status code Đoàn Trần Công Danh
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1629263759.git.congdanhqx@gmail.com \
--to=congdanhqx@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).