From: Christian Hesse <list@eworm.de>
To: Git Mailing List <git@vger.kernel.org>
Cc: Kousik Sanagavarapu <five231003@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
Hariom Verma <hariom18599@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Christian Hesse <mail@eworm.de>
Subject: [PATCH 1/2] t/lib-gpg: forcibly run a trustdb update
Date: Tue, 22 Aug 2023 15:03:14 +0200 [thread overview]
Message-ID: <20230822130315.71259-1-list@eworm.de> (raw)
In-Reply-To: <20230822150149.541ccb35@leda.eworm.net>
From: Christian Hesse <mail@eworm.de>
We want to compare output later, so randomly popping up 'gpg: checking
the trustdb' breaks the tests. Run the trustdb update forcibly.
Signed-off-by: Christian Hesse <mail@eworm.de>
---
t/lib-gpg.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/t/lib-gpg.sh b/t/lib-gpg.sh
index 4eebd9c2b5..83b83c9abb 100644
--- a/t/lib-gpg.sh
+++ b/t/lib-gpg.sh
@@ -45,6 +45,7 @@ test_lazy_prereq GPG '
"$TEST_DIRECTORY"/lib-gpg/keyring.gpg &&
gpg --homedir "${GNUPGHOME}" --import-ownertrust \
"$TEST_DIRECTORY"/lib-gpg/ownertrust &&
+ gpg --homedir "${GNUPGHOME}" --update-trustdb &&
gpg --homedir "${GNUPGHOME}" </dev/null >/dev/null \
--sign -u committer@example.com
;;
--
2.42.0
next prev parent reply other threads:[~2023-08-22 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 20:06 [PATCH 1/1] t6300: fix match with insecure memory Christian Hesse
2023-08-21 20:24 ` Christian Hesse
2023-08-21 20:25 ` [PATCH v2 " Christian Hesse
2023-08-22 7:54 ` Kousik Sanagavarapu
2023-08-22 9:04 ` Christian Hesse
2023-08-22 13:01 ` Christian Hesse
2023-08-22 13:03 ` Christian Hesse [this message]
2023-08-22 13:03 ` [PATCH 2/2] t/t6300: drop magic filtering Christian Hesse
2023-08-22 16:43 ` Eric Sunshine
2023-08-23 6:52 ` [PATCH v2 " Christian Hesse
2023-08-23 13:20 ` Kousik Sanagavarapu
2023-08-23 16:14 ` Junio C Hamano
2023-08-23 16:02 ` [PATCH " Junio C Hamano
2023-08-22 15:50 ` [PATCH v2 1/1] t6300: fix match with insecure memory 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:
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=20230822130315.71259-1-list@eworm.de \
--to=list@eworm.de \
--cc=christian.couder@gmail.com \
--cc=five231003@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hariom18599@gmail.com \
--cc=mail@eworm.de \
/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).