From: Patrick Steinhardt <ps@pks.im>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: "Jeff King" <peff@peff.net>,
git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
"Todd Zullinger" <tmz@pobox.com>,
"SZEDER Gábor" <szeder.dev@gmail.com>
Subject: Re: [PATCH v3 1/8] t5004: skip SHA-1-only test in SHA-256 repository
Date: Thu, 15 Oct 2026 07:43:52 +0200 [thread overview]
Message-ID: <atBoGE_R_EJhkEs0@pks.im> (raw)
In-Reply-To: <3888af48-339f-4b6a-ae84-88d0ad9caf07@gmail.com>
On Wed, Oct 14, 2026 at 08:34:09PM +0530, Kaartic Sivaraam wrote:
> On 10/14/26 16:04, Patrick Steinhardt wrote:
> > On Wed, Oct 14, 2026 at 05:07:46AM -0400, Jeff King wrote:
> > > On Wed, Oct 14, 2026 at 10:30:27AM +0200, Patrick Steinhardt wrote:
> > >
> > > > We're about to fix that typo in the next commit, but this will also
> > > > uncover that the above test case is broken when running in SHA-256
> > > > repositories. The extracted objects are SHA-1 objects, so extracting
> > > > them into a SHA-256 repository is not going to yield anything good. So
> > > > once we fix the Fedora-based job to enable breaking changes, which will
> > > > make tests use SHA-256 by default, the test will break.
> > > >
> > > > Fix this issue by adding the SHA1 prerequisite.
> > >
> > > Does that mean we'll basically never run the test once Git 3.0 shifts to
> > > sha256 by default? I guess we'll have a sha1 ci job (like we have sha256
> > > today), but would that job actually hit all the other prereqs?
> > >
> > > If we instead teach it to use its own repo, independent of the defaults,
> > > then we could run it everywhere (that allows all of the other prereqs).
> > >
>
> That indeed sounds like a good idea.
>
> I also wonder, though. How many CI jobs actually satisfy the prerequisite
> after the change? From a quick look and guessing via the time it took the
> t5004 jobs to run[1] it seems only the macOS jobs and on AlmaLinux 8 jobs
> run the test. The linux jobs don't seem to run it. I suppose this is
> expected behaviour.
>
> I wonder if it is worth mentioning in the commit message or not. FWIW, the
> "not a lot of jobs even exercise this." in the commit message made me want
> to confirm if this job runs at all after the change.
>
> [1]: https://github.com/git/git/actions/runs/38526140649?pr=2445
I guess it's less interesting which exact jobs run this, so I think I'll
keep this information out of the commit message for now.
Patrick
next prev parent reply other threads:[~2026-10-15 5:43 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 10:01 [PATCH 0/8] ci: some housekeeping and modernizations Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 1/8] t5004: skip SHA-1-only test in SHA-256 repository Patrick Steinhardt
2026-10-08 18:05 ` Junio C Hamano
2026-10-09 5:46 ` Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 2/8] ci: fix "fedora-breaking-changes-meson" job Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 3/8] ci: drop unused "linux-clang" logic Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 4/8] ci: switch away from unsupported i386/ubuntu image Patrick Steinhardt
2026-10-08 15:03 ` Todd Zullinger
2026-10-08 18:12 ` Junio C Hamano
2026-10-09 5:46 ` Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 5/8] ci: rename linux-TEST-vars job Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 6/8] ci: switch away from EOL'd Ubuntu version in linux-exotic Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 7/8] ci: drop now-dead Python 2 coverage Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 8/8] ci: drop redundant linux-reftable job Patrick Steinhardt
2026-10-08 18:18 ` Junio C Hamano
2026-10-09 5:55 ` Patrick Steinhardt
2026-10-09 20:22 ` Junio C Hamano
2026-10-09 11:31 ` [PATCH v2 0/8] ci: some housekeeping and modernizations Patrick Steinhardt
2026-10-09 11:31 ` [PATCH v2 1/8] t5004: skip SHA-1-only test in SHA-256 repository Patrick Steinhardt
2026-10-09 11:31 ` [PATCH v2 2/8] ci: fix "fedora-breaking-changes-meson" job Patrick Steinhardt
2026-10-09 11:32 ` [PATCH v2 3/8] ci: drop unused "linux-clang" logic Patrick Steinhardt
2026-10-09 11:32 ` [PATCH v2 4/8] ci: switch away from unsupported i386/ubuntu image Patrick Steinhardt
2026-10-09 11:32 ` [PATCH v2 5/8] ci: rename linux-TEST-vars job Patrick Steinhardt
2026-10-09 15:31 ` SZEDER Gábor
2026-10-13 7:21 ` Patrick Steinhardt
2026-10-13 14:47 ` Junio C Hamano
2026-10-14 7:03 ` Patrick Steinhardt
2026-10-09 11:32 ` [PATCH v2 6/8] ci: switch away from EOL'd Ubuntu version in linux-exotic Patrick Steinhardt
2026-10-09 11:32 ` [PATCH v2 7/8] ci: drop now-dead Python 2 coverage Patrick Steinhardt
2026-10-09 11:32 ` [PATCH v2 8/8] ci: improve reftable test coverage Patrick Steinhardt
2026-10-14 8:30 ` [PATCH v3 0/8] ci: some housekeeping and modernizations Patrick Steinhardt
2026-10-14 8:30 ` [PATCH v3 1/8] t5004: skip SHA-1-only test in SHA-256 repository Patrick Steinhardt
2026-10-14 9:07 ` Jeff King
2026-10-14 10:34 ` Patrick Steinhardt
2026-10-14 15:04 ` Kaartic Sivaraam
2026-10-15 5:43 ` Patrick Steinhardt [this message]
2026-10-14 8:30 ` [PATCH v3 2/8] ci: fix "fedora-breaking-changes-meson" job Patrick Steinhardt
2026-10-14 9:10 ` Jeff King
2026-10-14 10:35 ` Patrick Steinhardt
2026-10-14 11:07 ` Jeff King
2026-10-14 11:18 ` Patrick Steinhardt
2026-10-14 8:30 ` [PATCH v3 3/8] ci: drop unused "linux-clang" logic Patrick Steinhardt
2026-10-14 8:30 ` [PATCH v3 4/8] ci: switch away from unsupported i386/ubuntu image Patrick Steinhardt
2026-10-14 9:17 ` Jeff King
2026-10-14 10:35 ` Patrick Steinhardt
2026-10-14 11:08 ` Jeff King
2026-10-14 8:30 ` [PATCH v3 5/8] ci: rename linux-TEST-vars job Patrick Steinhardt
2026-10-14 9:17 ` Jeff King
2026-10-14 8:30 ` [PATCH v3 6/8] ci: switch away from EOL'd Ubuntu version in linux-feature-testbed Patrick Steinhardt
2026-10-14 9:18 ` Jeff King
2026-10-14 8:30 ` [PATCH v3 7/8] ci: drop now-dead Python 2 coverage Patrick Steinhardt
2026-10-14 8:30 ` [PATCH v3 8/8] ci: improve reftable test coverage Patrick Steinhardt
2026-10-14 9:21 ` Jeff King
2026-10-14 10:35 ` Patrick Steinhardt
2026-10-14 11:13 ` Jeff King
2026-10-14 11:18 ` Patrick Steinhardt
2026-10-14 13:47 ` Jeff King
2026-10-14 9:22 ` [PATCH v3 0/8] ci: some housekeeping and modernizations Jeff King
2026-10-14 14:28 ` Junio C Hamano
2026-10-15 5:43 ` Patrick Steinhardt
2026-10-15 6:57 ` [PATCH v4 " Patrick Steinhardt
2026-10-15 6:57 ` [PATCH v4 1/8] t5004: fix test creating an archive with large objects under SHA256 Patrick Steinhardt
2026-10-15 6:57 ` [PATCH v4 2/8] ci: fix "fedora-breaking-changes-meson" job Patrick Steinhardt
2026-10-15 6:57 ` [PATCH v4 3/8] ci: drop unused "linux-clang" logic Patrick Steinhardt
2026-10-15 8:36 ` Kaartic Sivaraam
2026-10-15 9:31 ` Patrick Steinhardt
2026-10-15 6:57 ` [PATCH v4 4/8] ci: switch away from unsupported i386/ubuntu image Patrick Steinhardt
2026-10-15 6:57 ` [PATCH v4 5/8] ci: rename linux-TEST-vars job Patrick Steinhardt
2026-10-15 6:57 ` [PATCH v4 6/8] ci: switch away from EOL'd Ubuntu version in linux-feature-testbed Patrick Steinhardt
2026-10-15 6:57 ` [PATCH v4 7/8] ci: drop now-dead Python 2 coverage Patrick Steinhardt
2026-10-15 6:57 ` [PATCH v4 8/8] ci: improve reftable test coverage Patrick Steinhardt
2026-10-15 7:06 ` [PATCH v4 0/8] ci: some housekeeping and modernizations Jeff King
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=atBoGE_R_EJhkEs0@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=peff@peff.net \
--cc=szeder.dev@gmail.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