From: Junio C Hamano <gitster@pobox.com>
To: Todd Zullinger <tmz@pobox.com>
Cc: git@vger.kernel.org, Andrew Kreimer <algonell@gmail.com>,
Taylor Blau <me@ttaylorr.com>
Subject: Re: [PATCH] t1016: make sure to use specified GPG
Date: Sun, 12 Oct 2025 08:11:05 -0700 [thread overview]
Message-ID: <xmqq1pn85f5i.fsf@gitster.g> (raw)
In-Reply-To: <aOu59eVs7tK6pCoF@teonanacatl.net> (Todd Zullinger's message of "Sun, 12 Oct 2025 10:23:49 -0400")
Todd Zullinger <tmz@pobox.com> writes:
> Interesting. And well-spotted.
>
> This _does_ seem to resolve the failures in our CI and in
> the Fedora build system. I was able to run a few test
> builds. With this fix, the tests were successful where they
> were not without it.
>
> I remember suspecting the gpg calls were not using the
> wrapper command in gpg.program. I even tried forcing the
> --faked-system-time for all the tests to check that theory,
> unsuccessfully.
>
> Oddly, I ran into test failures after fixing the GPG2 prereq
> long before c348192afe (t1016: clean up style, 2024-10-22)
> was in place. Perhaps I was hitting a different issue
> initially? Then, when I looked at it again I didn't think
> about gpg.program again, since I'd already tried to force
> the gpg wrapper which sets --faked-system-time.
>
> It's both annoying and embarrassing if it is that simple and
> I missed it after looking a few times, to be sure. But I'll
> be happy with the end result all the same. :)
FWIW, GitHub CI jobs are failing t1016 at the tip of 'seen' (which
has this change), but only some and not all the jobs, which may
indicate there are timeing-dependent flakes involved. I didn't dig
further, though.
>> t/t1016-compatObjectFormat.sh | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/t/t1016-compatObjectFormat.sh b/t/t1016-compatObjectFormat.sh
>> index 8341a2fe83..cb6d308f1d 100755
>> --- a/t/t1016-compatObjectFormat.sh
>> +++ b/t/t1016-compatObjectFormat.sh
>> @@ -116,7 +116,7 @@ do
>> git config core.repositoryformatversion 1 &&
>> git config extensions.objectformat $hash &&
>> git config extensions.compatobjectformat $(compat_hash $hash) &&
>> - test_config gpg.program $TEST_DIRECTORY/t1016/gpg &&
>> + git config gpg.program $TEST_DIRECTORY/t1016/gpg &&
>> echo "Hello World!" >hello &&
>> eval hello_${hash}_oid=$(git hash-object hello) &&
>> git update-index --add hello &&
next prev parent reply other threads:[~2025-10-12 15:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 21:14 [PATCH] t1016: make sure to use specified GPG Junio C Hamano
2025-10-12 14:23 ` Todd Zullinger
2025-10-12 15:11 ` Junio C Hamano [this message]
2025-10-12 18:31 ` Todd Zullinger
2025-10-23 20:52 ` Junio C Hamano
2025-10-24 1:52 ` Todd Zullinger
2025-10-12 20:40 ` Andrew Kreimer
2025-10-13 15:38 ` 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=xmqq1pn85f5i.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=algonell@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=tmz@pobox.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).