From: Todd Zullinger <tmz@pobox.com>
To: git@vger.kernel.org
Cc: Kousik Sanagavarapu <five231003@gmail.com>,
"Eric W . Biederman" <ebiederm@xmission.com>
Subject: [PATCH 0/2] t/lib-gpg: ensure GNUPGHOME is created as needed
Date: Wed, 3 Jul 2024 11:37:30 -0400 [thread overview]
Message-ID: <20240703153738.916469-1-tmz@pobox.com> (raw)
Hi,
While reviewing my local build logs, I noticed a number of tests being
skipped unintentionally. I had not done so with any of the 2.45.0
releases, unfortunately, which is when this began.
92 of the 202 tests in t1016-compatObjectFormat.sh are skipped due to
the GNUPGHOME directory missing, e.g.:
ok 5 # SKIP create a sha1 signed commit (missing GPG2)
ok 6 # SKIP create a sha1 signed tag (missing GPG2)
ok 8 # SKIP create another sha1 signed tag (missing GPG2)
ok 9 # SKIP merge the sha1 branches together (missing GPG2)
With these changes, they are all run (successfully). :)
I presume that they have been skipped in the Github CI runs as well,
but I don't know that the logs show enough detail to confirm that.
Thanks,
Todd
Todd Zullinger (2):
t/lib-gpg: add prepare_gnupghome() to create GNUPGHOME dir
t/lib-gpg: call prepare_gnupghome() in GPG2 prereq
t/lib-gpg.sh | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
--
2.45.2
next reply other threads:[~2024-07-03 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 15:37 Todd Zullinger [this message]
2024-07-03 15:37 ` [PATCH 1/2] t/lib-gpg: add prepare_gnupghome() to create GNUPGHOME dir Todd Zullinger
2024-07-03 15:37 ` [PATCH 2/2] t/lib-gpg: call prepare_gnupghome() in GPG2 prereq Todd Zullinger
2024-07-03 16:29 ` [PATCH 0/2] t/lib-gpg: ensure GNUPGHOME is created as needed Todd Zullinger
2025-02-28 15:26 ` Todd Zullinger
2025-10-26 1:25 ` Junio C Hamano
2025-10-27 16:16 ` Eric W. Biederman
2025-10-27 17:38 ` Junio C Hamano
2025-10-27 19:03 ` Eric W. Biederman
2025-10-27 19:32 ` Eric W. Biederman
2025-10-27 20:32 ` Junio C Hamano
2025-10-28 16:01 ` [PATCH] t1016-compatObjectFormat: Really freeze time for reproduciblity Eric W. Biederman
2025-10-28 17:15 ` Junio C Hamano
2025-10-29 3:05 ` Todd Zullinger
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=20240703153738.916469-1-tmz@pobox.com \
--to=tmz@pobox.com \
--cc=ebiederm@xmission.com \
--cc=five231003@gmail.com \
--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).