From: "René Scharfe" <l.s.r@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>,
Kousik Sanagavarapu <five231003@gmail.com>,
Hariom Verma <hariom18599@gmail.com>,
Jaydeep Das <jaydeepjd.8914@gmail.com>,
Nsengiyumva Wilberforce <nsengiyumvawilberforce@gmail.com>,
Christian Couder <christian.couder@gmail.com>
Subject: Re: [PATCH] t6300: fix setup with GPGSSH but without GPG
Date: Mon, 17 Jul 2023 19:12:47 +0200 [thread overview]
Message-ID: <183f69ff-8b6b-80a5-4d25-d58d25ae5b5f@web.de> (raw)
In-Reply-To: <xmqqwmyyik2o.fsf@gitster.g>
Am 17.07.23 um 18:22 schrieb Junio C Hamano:
> René Scharfe <l.s.r@web.de> writes:
>
>> In a test introduced by 26c9c03f0a (ref-filter: add new "signature"
>> atom, 2023-06-04) the file named "file" is added by a setup step that
>> requires GPG and modified by a second setup step that requires GPGSSH.
>> Systems lacking the first prerequisite skip the initial setup step and
>> then "git commit -a" in the second one doesn't find the modified file.
>> Add it explicitly.
>>
>> Signed-off-by: René Scharfe <l.s.r@web.de>
>> ---
>> t/t6300-for-each-ref.sh | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> Thanks for good eyes.
>
> I guess a box without GPG is not so uncommon, and even such a box
> can reasonably be expected to have SSH on it, so I would believe if
> this was discovered on a real development box, but is that how you
> found this? Or have you invented a nice test helper that lets you
> pick random set of prerequisites and try permutations of having and
> not having them, or something nice like that?
The test actually did fail on my machine.
Running tests with all possible permutations of prerequisites would be
nice, but sounds very expensive -- there must be billions of them! But
there are only a few per test script, I imagine. Collecting all found
prerequisites for each script and providing a way to force-disable them
individually could make testing them all feasible. Nice idea!
René
prev parent reply other threads:[~2023-07-17 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 8:17 [PATCH] t6300: fix setup with GPGSSH but without GPG René Scharfe
2023-07-17 6:33 ` Christian Couder
2023-07-17 16:22 ` Junio C Hamano
2023-07-17 17:12 ` René Scharfe [this message]
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=183f69ff-8b6b-80a5-4d25-d58d25ae5b5f@web.de \
--to=l.s.r@web.de \
--cc=christian.couder@gmail.com \
--cc=five231003@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hariom18599@gmail.com \
--cc=jaydeepjd.8914@gmail.com \
--cc=nsengiyumvawilberforce@gmail.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).