{"thread":{"id":"66489","subject":"[PATCH 0/8] ci: some housekeeping and modernizations","startedAt":"2026-10-08T10:01:18Z","lastAt":"2026-10-19T20:07:17Z","messageCount":77,"participants":["Patrick Steinhardt","Todd Zullinger","Junio C Hamano","SZEDER Gábor","Jeff King","Kaartic Sivaraam"],"isPatch":true,"patchVersion":1,"patchTotal":8},"messages":[{"id":"554473","messageId":"20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im","threadId":"66489","inReplyTo":null,"subject":"[PATCH 0/8] ci: some housekeeping and modernizations","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-08T10:01:18Z","receivedAt":"2026-10-08T10:01:18Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"Hi,\n\nthis patch series is a result from the discussions in [1]. It fixes a\ncouple of smaller issues in our CI and bumps jobs that use EOL Docker\nimages to instead use supported ones.\n\nPassing test runs can be found at [2] and [3] for GitLab and GitHub,\nrespectively.\n\nNote that I've also merged the Meson changes (ps/meson-improvements at\nce4a600322 (gitlab-ci: fix hanging MSVC jobs, 2026-09-24)) in there so\nthat GitLab passes, but those are not strictly required as a dependency.\n\nThanks!\n\nPatrick\n\n[1]: <20260906151137.GA328152@coredump.intra.peff.net>\n[2]: https://gitlab.com/gitlab-org/git/-/merge_requests/687\n[3]: https://github.com/git/git/pull/2445\n\n---\nPatrick Steinhardt (8):\n      t5004: skip SHA-1-only test in SHA-256 repository\n      ci: fix \"fedora-breaking-changes-meson\" job\n      ci: drop unused \"linux-clang\" logic\n      ci: switch away from unsupported i386/ubuntu image\n      ci: rename linux-TEST-vars job\n      ci: switch away from EOL'd Ubuntu version in linux-exotic\n      ci: drop now-dead Python 2 coverage\n      ci: drop redundant linux-reftable job\n\n .github/workflows/main.yml      | 12 +++---------\n .gitlab-ci.yml                  | 12 +++---------\n ci/install-dependencies.sh      |  8 ++------\n ci/lib.sh                       | 13 ++-----------\n ci/run-build-and-tests.sh       | 10 +++-------\n t/t5004-archive-corner-cases.sh |  2 +-\n 6 files changed, 14 insertions(+), 43 deletions(-)\n\n\n---\nbase-commit: 8e383dedc6bbc4fd7bbb203512fbf2eafc151e04\nchange-id: 20261008-pks-ci-housekeeping-4cf7fac3b0df\n\n\n"},{"id":"554474","messageId":"20261008-pks-ci-housekeeping-v1-1-baf015c589c0@pks.im","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im","subject":"[PATCH 1/8] t5004: skip SHA-1-only test in SHA-256 repository","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-08T10:01:19Z","receivedAt":"2026-10-08T10:01:19Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"One of the tests in t5004 extracts a ZIP file that contains some objects\nlarger than 4GB and then double-checks whether we can read and archive\nsuch an object. That test has a bunch of prerequities: it requires a 64\nbit `long`, unzip with 64-bit support and it only runs when EXPENSIVE is\nenabled. Consequently, not a lot of jobs even exercise this.\n\nOne of the jobs that does run it though our Fedora-based job, as it\nticks all the necessary boxes. But that job was silently broken: while\nthe intent was to run on Fedora with breaking changes enabled, they are\nin fact disabled due to a typo.\n\nWe're about to fix that typo in the next commit, but this will also\nuncover that the above test case is broken when running in SHA-256\nrepositories. The extracted objects are SHA-1 objects, so extracting\nthem into a SHA-256 repository is not going to yield anything good. So\nonce we fix the Fedora-based job to enable breaking changes, which will\nmake tests use SHA-256 by default, the test will break.\n\nFix this issue by adding the SHA1 prerequisite.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n t/t5004-archive-corner-cases.sh | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/t/t5004-archive-corner-cases.sh b/t/t5004-archive-corner-cases.sh\nindex 768b0ff85d..c9c879cc5f 100755\n--- a/t/t5004-archive-corner-cases.sh\n+++ b/t/t5004-archive-corner-cases.sh\n@@ -185,7 +185,7 @@ test_expect_success EXPENSIVE,UNZIP,UNZIP_ZIP64_SUPPORT \\\n \t\"$GIT_UNZIP\" -t many-big.zip\n '\n \n-test_expect_success EXPENSIVE,LONG_IS_64BIT,UNZIP,UNZIP_ZIP64_SUPPORT,ZIPINFO \\\n+test_expect_success EXPENSIVE,LONG_IS_64BIT,UNZIP,UNZIP_ZIP64_SUPPORT,ZIPINFO,SHA1 \\\n \t'zip archive with files bigger than 4GB' '\n \t# Pack created with:\n \t#   dd if=/dev/zero of=file bs=1M count=4100 && git hash-object -w file\n\n-- \n2.56.0.406.ga2d225a756.dirty\n\n\n"},{"id":"554475","messageId":"20261008-pks-ci-housekeeping-v1-2-baf015c589c0@pks.im","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im","subject":"[PATCH 2/8] ci: fix \"fedora-breaking-changes-meson\" job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-08T10:01:20Z","receivedAt":"2026-10-08T10:01:20Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"fedora-breaking-changes-meson\" job exercises Git with breaking\nchanges enabled on Fedora with Meson. There's a typo in our CI scripts\nthough, which has the effect that the build does not enable breaking\nchanges by accident.\n\nFix the typo.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n ci/run-build-and-tests.sh | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex 6a3b43b366..bc5058c917 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -18,7 +18,7 @@ almalinux-*|debian-*|fedora-*|linux-*)\n esac\n \n case \"$jobname\" in\n-fedora-breaking-changes-musl|linux-breaking-changes)\n+fedora-breaking-changes-meson|linux-breaking-changes)\n \texport WITH_BREAKING_CHANGES=YesPlease\n \tMESONFLAGS=\"$MESONFLAGS -Dbreaking_changes=true\"\n \t;;\n\n-- \n2.56.0.406.ga2d225a756.dirty\n\n\n"},{"id":"554476","messageId":"20261008-pks-ci-housekeeping-v1-3-baf015c589c0@pks.im","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im","subject":"[PATCH 3/8] ci: drop unused \"linux-clang\" logic","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-08T10:01:21Z","receivedAt":"2026-10-08T10:01:21Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"In d88d727143 (ci: drop linux-clang job, 2023-06-01) we have dropped the\n\"linux-clang\" job because another job already uses Clang anyway. But we\nforgot to also drop the logic in \"ci/run-build-and-tests.sh\", so we now\nhave some unused logic in there.\n\nDrop it.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n ci/run-build-and-tests.sh | 4 ----\n 1 file changed, 4 deletions(-)\n\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex bc5058c917..23e87cbbd6 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -37,10 +37,6 @@ linux-TEST-vars)\n \texport GIT_TEST_CHECKOUT_WORKERS=2\n \texport GIT_TEST_PACK_USE_BITMAP_BOUNDARY_TRAVERSAL=1\n \t;;\n-linux-clang)\n-\texport NO_RUST=UnfortunatelyYes\n-\texport GIT_TEST_DEFAULT_HASH=sha1\n-\t;;\n linux-sha256)\n \texport GIT_TEST_DEFAULT_HASH=sha256\n \t;;\n\n-- \n2.56.0.406.ga2d225a756.dirty\n\n\n"},{"id":"554477","messageId":"20261008-pks-ci-housekeeping-v1-4-baf015c589c0@pks.im","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im","subject":"[PATCH 4/8] ci: switch away from unsupported i386/ubuntu image","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-08T10:01:22Z","receivedAt":"2026-10-08T10:01:22Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The linux32 job is used to exercise Git on a 32 bit platform. That job\nuses i386/ubuntu:20.04 though, and that version of Ubuntu is end of life\nnowadays. Furthermore, Ubuntu has dropped support for 32 bit entirely\nwith the 20.04 release, so we cannot easily upgrade it to a more recent\nimage anymore.\n\nSwitch the job over to use i386/debian instead. Note that starting with\nDebian 13, support for i386 has been reduced [1]. But Debian still\nreleases 32 bit Docker images for the latest release nowadays, so we\nwill have coverage until at least 2030.\n\n[1]: https://www.debian.org/releases/trixie/release-notes/issues.en.html#i386-reduced-support\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 3 +--\n .gitlab-ci.yml             | 3 +--\n ci/install-dependencies.sh | 6 +-----\n ci/lib.sh                  | 2 +-\n 4 files changed, 4 insertions(+), 10 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex b229739be8..6d1e37c8f1 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -431,9 +431,8 @@ jobs:\n           cc: gcc\n         - jobname: linux-musl-meson\n           image: alpine:latest\n-        # Supported until 2025-04-02.\n         - jobname: linux32\n-          image: i386/ubuntu:20.04\n+          image: i386/debian:latest\n         # A RHEL 8 compatible distro.  Supported until 2029-05-31.\n         - jobname: almalinux-8\n           image: almalinux:8\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 3f24835500..7d972f0c8b 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -65,9 +65,8 @@ test:linux:\n         CC: gcc\n       - jobname: linux-musl-meson\n         image: alpine:latest\n-        # Supported until 2025-04-02.\n       - jobname: linux32\n-        image: i386/ubuntu:20.04\n+        image: i386/debian:latest\n       # A RHEL 8 compatible distro.  Supported until 2029-05-31.\n       - jobname: almalinux-8\n         image: almalinux:8\ndiff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh\nindex d57dce5663..8783b48951 100755\n--- a/ci/install-dependencies.sh\n+++ b/ci/install-dependencies.sh\n@@ -39,7 +39,7 @@ fedora-*|almalinux-*)\n \tdnf -yq update >/dev/null &&\n \tdnf -yq install shadow-utils sudo make pkg-config gcc findutils diffutils perl python3 gawk gettext zlib-devel expat-devel openssl-devel curl-devel pcre2-devel $MESON_DEPS cargo >/dev/null\n \t;;\n-ubuntu-*|i386/ubuntu-*|debian-*)\n+ubuntu-*|i386/debian-*|debian-*)\n \t# Required so that apt doesn't wait for user input on certain packages.\n \texport DEBIAN_FRONTEND=noninteractive\n \n@@ -48,10 +48,6 @@ ubuntu-*|i386/ubuntu-*|debian-*)\n \t\tSVN='libsvn-perl subversion'\n \t\tLANGUAGES='language-pack-is'\n \t\t;;\n-\ti386/ubuntu-*)\n-\t\tSVN=\n-\t\tLANGUAGES='language-pack-is'\n-\t\t;;\n \t*)\n \t\tSVN='libsvn-perl subversion'\n \t\tLANGUAGES='locales-all'\ndiff --git a/ci/lib.sh b/ci/lib.sh\nindex c6ccbf8c17..d99e7b9da1 100755\n--- a/ci/lib.sh\n+++ b/ci/lib.sh\n@@ -262,7 +262,7 @@ then\n \t\tCI_OS_NAME=osx\n \t\tJOBS=$(nproc)\n \t\t;;\n-\t*,almalinux:*|*,alpine:*|*,debian:*|*,fedora:*|*,ubuntu:*|*,i386/ubuntu:*)\n+\t*,almalinux:*|*,alpine:*|*,debian:*|*,fedora:*|*,ubuntu:*|*,i386/debian:*)\n \t\tCI_OS_NAME=linux\n \t\tJOBS=$(nproc)\n \t\t;;\n\n-- \n2.56.0.406.ga2d225a756.dirty\n\n\n"},{"id":"554478","messageId":"20261008-pks-ci-housekeeping-v1-5-baf015c589c0@pks.im","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im","subject":"[PATCH 5/8] ci: rename linux-TEST-vars job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-08T10:01:23Z","receivedAt":"2026-10-08T10:01:23Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"linux-TEST-vars\" job exercises Git with a bunch of non-default\noptions enabled. The name of that job makes you want to cry though due\nto the weird upper-casing and because it doesn't really tell you what it\neven intends to do.\n\nRename the job to \"linux-exotic\" instead.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 2 +-\n .gitlab-ci.yml             | 2 +-\n ci/run-build-and-tests.sh  | 2 +-\n 3 files changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex 6d1e37c8f1..d7a301ec98 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -408,7 +408,7 @@ jobs:\n         - jobname: linux-reftable\n           image: ubuntu:rolling\n           cc: clang\n-        - jobname: linux-TEST-vars\n+        - jobname: linux-exotic\n           image: ubuntu:20.04\n           cc: gcc\n           cc_package: gcc-8\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 7d972f0c8b..27a16ed086 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -42,7 +42,7 @@ test:linux:\n       - jobname: linux-reftable\n         image: ubuntu:rolling\n         CC: clang\n-      - jobname: linux-TEST-vars\n+      - jobname: linux-exotic\n         image: ubuntu:20.04\n         CC: gcc\n         CC_PACKAGE: gcc-8\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex 23e87cbbd6..9381ff8893 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -22,7 +22,7 @@ fedora-breaking-changes-meson|linux-breaking-changes)\n \texport WITH_BREAKING_CHANGES=YesPlease\n \tMESONFLAGS=\"$MESONFLAGS -Dbreaking_changes=true\"\n \t;;\n-linux-TEST-vars)\n+linux-exotic)\n \texport OPENSSL_SHA1_UNSAFE=YesPlease\n \texport GIT_TEST_SPLIT_INDEX=yes\n \texport GIT_TEST_FULL_IN_PACK_ARRAY=true\n\n-- \n2.56.0.406.ga2d225a756.dirty\n\n\n"},{"id":"554479","messageId":"20261008-pks-ci-housekeeping-v1-6-baf015c589c0@pks.im","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im","subject":"[PATCH 6/8] ci: switch away from EOL'd Ubuntu version in linux-exotic","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-08T10:01:24Z","receivedAt":"2026-10-08T10:01:24Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"linux-exotic\" job still uses Ubuntu 20.04, which is end of life\nnowadays and starting to show some cracks. Switch it over to use the\n\"latest\" tag instead so that we don't have to constantly update it\nanymore.\n\nNow arguably, this reduces test coverage for old versions of Ubuntu.\nBut \"latest\" at least points to the most up-to-date LTS release of\nUbuntu, compared to the \"rolling\" tag that uses the latest release\nregardless of the LTS status. So while \"latest\" and \"rolling\" are the\nsame right now, that's not always the case.\n\nFurthermore, we have other jobs that test with ancient versions of\nLinux, like for example the one that uses AlmaLinux 8 (2021, originally\ntracking RHEL 8 from 2019) or Debian 12 (2023).\n\nNote that this also requires us to switch away from GCC 8, which is not\nsupported by Ubuntu 26.04 anymore. Instead we simply use the default\nversion of GCC.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 4 +---\n .gitlab-ci.yml             | 4 +---\n 2 files changed, 2 insertions(+), 6 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex d7a301ec98..5b772dab55 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -409,9 +409,7 @@ jobs:\n           image: ubuntu:rolling\n           cc: clang\n         - jobname: linux-exotic\n-          image: ubuntu:20.04\n-          cc: gcc\n-          cc_package: gcc-8\n+          image: ubuntu:latest\n         - jobname: linux-breaking-changes\n           cc: gcc\n           image: ubuntu:rolling\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 27a16ed086..de40434ae3 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -43,9 +43,7 @@ test:linux:\n         image: ubuntu:rolling\n         CC: clang\n       - jobname: linux-exotic\n-        image: ubuntu:20.04\n-        CC: gcc\n-        CC_PACKAGE: gcc-8\n+        image: ubuntu:latest\n       - jobname: linux-breaking-changes\n         image: ubuntu:rolling\n         CC: gcc\n\n-- \n2.56.0.406.ga2d225a756.dirty\n\n\n"},{"id":"554480","messageId":"20261008-pks-ci-housekeeping-v1-7-baf015c589c0@pks.im","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im","subject":"[PATCH 7/8] ci: drop now-dead Python 2 coverage","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-08T10:01:25Z","receivedAt":"2026-10-08T10:01:25Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"In the preceding commit we've dropped the last job that still used\nUbuntu 20.04. We still had some conditional logic for that specific\nimage that made us use Python 2 instead of Python 3, but this is dead\ncode now.\n\nWe could of course exercise Python 2 in any of our other CI jobs. But it\nreached end of life in 2020 already, and none of the distros that we use\nhave it packaged anymore. Furthermore, it seems like the world has\nfinally adapted to Python 3. So it doesn't feel all that useful to still\nexercise it.\n\nDrop the logic and instead use Python 3 unconditionally.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n ci/install-dependencies.sh |  2 +-\n ci/lib.sh                  | 11 +----------\n 2 files changed, 2 insertions(+), 11 deletions(-)\n\ndiff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh\nindex 8783b48951..4b1733ad15 100755\n--- a/ci/install-dependencies.sh\n+++ b/ci/install-dependencies.sh\n@@ -61,7 +61,7 @@ ubuntu-*|i386/debian-*|debian-*)\n \t\ttcl tk gettext zlib1g-dev perl-modules liberror-perl libauthen-sasl-perl \\\n \t\tlibemail-valid-perl libio-pty-perl libio-socket-ssl-perl libnet-smtp-ssl-perl libdbd-sqlite3-perl libcgi-pm-perl \\\n \t\tlibsecret-1-dev libpcre2-dev meson ninja-build pkg-config cargo \\\n-\t\t${CC_PACKAGE:-${CC:-gcc}} $PYTHON_PACKAGE\n+\t\t${CC_PACKAGE:-${CC:-gcc}} python3\n \n \t# Starting with Ubuntu 25.10, sudo can now be provided via either\n \t# sudo(1) or sudo-rs(1), with the latter being the default. The problem\ndiff --git a/ci/lib.sh b/ci/lib.sh\nindex d99e7b9da1..3ec10488d4 100755\n--- a/ci/lib.sh\n+++ b/ci/lib.sh\n@@ -335,16 +335,7 @@ esac\n \n case \"$distro\" in\n ubuntu-*)\n-\t# Python 2 is end of life, and Ubuntu 23.04 and newer don't actually\n-\t# have it anymore. We thus only test with Python 2 on older LTS\n-\t# releases.\n-\tif test \"$distro\" = \"ubuntu-20.04\"\n-\tthen\n-\t\tPYTHON_PACKAGE=python2\n-\telse\n-\t\tPYTHON_PACKAGE=python3\n-\tfi\n-\tMAKEFLAGS=\"$MAKEFLAGS PYTHON_PATH=/usr/bin/$PYTHON_PACKAGE\"\n+\tMAKEFLAGS=\"$MAKEFLAGS PYTHON_PATH=/usr/bin/python3\"\n \n \texport GIT_TEST_HTTPD=true\n \n\n-- \n2.56.0.406.ga2d225a756.dirty\n\n\n"},{"id":"554481","messageId":"20261008-pks-ci-housekeeping-v1-8-baf015c589c0@pks.im","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im","subject":"[PATCH 8/8] ci: drop redundant linux-reftable job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-08T10:01:26Z","receivedAt":"2026-10-08T10:01:26Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"linux-reftable\" job exercises Git with reftables as its default\nbackend. But this job is arguably redundant because we already have the\n\"linux-reftable-leaks\" job that exercises reftables with the leak\nsanitizer enabled, and it is unlikely that we will catch any extra bugs\nwith the leak sanitizer disabled.\n\nDrop the job.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 3 ---\n .gitlab-ci.yml             | 3 ---\n ci/run-build-and-tests.sh  | 2 +-\n 3 files changed, 1 insertion(+), 7 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex 5b772dab55..4be3f2337d 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -405,9 +405,6 @@ jobs:\n         - jobname: linux-sha256\n           image: ubuntu:rolling\n           cc: clang\n-        - jobname: linux-reftable\n-          image: ubuntu:rolling\n-          cc: clang\n         - jobname: linux-exotic\n           image: ubuntu:latest\n         - jobname: linux-breaking-changes\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex de40434ae3..f0424bab5b 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -39,9 +39,6 @@ test:linux:\n       - jobname: linux-sha256\n         image: ubuntu:rolling\n         CC: clang\n-      - jobname: linux-reftable\n-        image: ubuntu:rolling\n-        CC: clang\n       - jobname: linux-exotic\n         image: ubuntu:latest\n       - jobname: linux-breaking-changes\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex 9381ff8893..df63e79319 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -40,7 +40,7 @@ linux-exotic)\n linux-sha256)\n \texport GIT_TEST_DEFAULT_HASH=sha256\n \t;;\n-linux-reftable|linux-reftable-leaks|osx-reftable)\n+linux-reftable-leaks|osx-reftable)\n \texport GIT_TEST_DEFAULT_REF_STORAGE_FORMAT=reftable\n \t;;\n \n\n-- \n2.56.0.406.ga2d225a756.dirty\n\n\n"},{"id":"554506","messageId":"20261008150336.CzZS-oEZ@teonanacatl.net","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-4-baf015c589c0@pks.im","subject":"Re: [PATCH 4/8] ci: switch away from unsupported i386/ubuntu image","fromName":"Todd Zullinger","fromEmail":"tmz@pobox.com","sentAt":"2026-10-08T15:03:36Z","receivedAt":"2026-10-08T15:03:36Z","isPatch":true,"sender":{"key":"tmz@pobox.com","avatar":"https://avatars.githubusercontent.com/u/806319?v=4"},"body":"Patrick Steinhardt wrote:\n> The linux32 job is used to exercise Git on a 32 bit platform. That job\n> uses i386/ubuntu:20.04 though, and that version of Ubuntu is end of life\n> nowadays. Furthermore, Ubuntu has dropped support for 32 bit entirely\n> with the 20.04 release, so we cannot easily upgrade it to a more recent\n> image anymore.\n\nShould \"with the 20.04 release\" be 22.04 (or whatever\nrelease dropped i386)?\n\nWe've been using 20.04, so i386 support wasn't dropped\nthere, I presume.\n\nYou could say \"after the 20.04 release\" perhaps, but that\nseems less useful.  In that case, you avoid using a version\nat all, e.g. \"dropped support ...  entirely in subsequent\nreleases\" or something.\n\nCheers,\n\n-- \nTodd\n\n"},{"id":"554518","messageId":"xmqqa4oo1313.fsf@gitster.g","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-1-baf015c589c0@pks.im","subject":"Re: [PATCH 1/8] t5004: skip SHA-1-only test in SHA-256 repository","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-08T18:05:28Z","receivedAt":"2026-10-08T18:05:28Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n> One of the tests in t5004 extracts a ZIP file that contains some objects\n> larger than 4GB and then double-checks whether we can read and archive\n> such an object. That test has a bunch of prerequities: it requires a 64\n> bit `long`, unzip with 64-bit support and it only runs when EXPENSIVE is\n> enabled. Consequently, not a lot of jobs even exercise this.\n>\n> One of the jobs that does run it though our Fedora-based job, as it\n\n\"One of the jobs that does run it though\" IS \"our Fedora-based job\"?\n\n> ticks all the necessary boxes. But that job was silently broken: while\n> the intent was to run on Fedora with breaking changes enabled, they are\n> in fact disabled due to a typo.\n>\n> We're about to fix that typo in the next commit, but this will also\n> uncover that the above test case is broken when running in SHA-256\n> repositories. The extracted objects are SHA-1 objects, so extracting\n> them into a SHA-256 repository is not going to yield anything good. So\n> once we fix the Fedora-based job to enable breaking changes, which will\n> make tests use SHA-256 by default, the test will break.\n>\n> Fix this issue by adding the SHA1 prerequisite.\n>\n> Signed-off-by: Patrick Steinhardt <ps@pks.im>\n> ---\n>  t/t5004-archive-corner-cases.sh | 2 +-\n>  1 file changed, 1 insertion(+), 1 deletion(-)\n>\n> diff --git a/t/t5004-archive-corner-cases.sh b/t/t5004-archive-corner-cases.sh\n> index 768b0ff85d..c9c879cc5f 100755\n> --- a/t/t5004-archive-corner-cases.sh\n> +++ b/t/t5004-archive-corner-cases.sh\n> @@ -185,7 +185,7 @@ test_expect_success EXPENSIVE,UNZIP,UNZIP_ZIP64_SUPPORT \\\n>  \t\"$GIT_UNZIP\" -t many-big.zip\n>  '\n>  \n> -test_expect_success EXPENSIVE,LONG_IS_64BIT,UNZIP,UNZIP_ZIP64_SUPPORT,ZIPINFO \\\n> +test_expect_success EXPENSIVE,LONG_IS_64BIT,UNZIP,UNZIP_ZIP64_SUPPORT,ZIPINFO,SHA1 \\\n>  \t'zip archive with files bigger than 4GB' '\n>  \t# Pack created with:\n>  \t#   dd if=/dev/zero of=file bs=1M count=4100 && git hash-object -w file\n\n"},{"id":"554520","messageId":"xmqq4iew12pw.fsf@gitster.g","threadId":"66489","inReplyTo":"20261008150336.CzZS-oEZ@teonanacatl.net","subject":"Re: [PATCH 4/8] ci: switch away from unsupported i386/ubuntu image","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-08T18:12:11Z","receivedAt":"2026-10-08T18:12:11Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Todd Zullinger <tmz@pobox.com> writes:\n\n> Patrick Steinhardt wrote:\n>> The linux32 job is used to exercise Git on a 32 bit platform. That job\n>> uses i386/ubuntu:20.04 though, and that version of Ubuntu is end of life\n>> nowadays. Furthermore, Ubuntu has dropped support for 32 bit entirely\n>> with the 20.04 release, so we cannot easily upgrade it to a more recent\n>> image anymore.\n>\n> Should \"with the 20.04 release\" be 22.04 (or whatever\n> release dropped i386)?\n\nFWIW, I read the above to mean \"32bit support, together with 20.04,\nare now gone\", and did not feel any need for rephrasing.  But\nreading it again, yes, it can be read both ways.\n\n    Ubuntu has dropped support for 32-bit entirely, together with\n    20.04 release, so upgrading it to a more recent image would not\n    help us keeping 32-bit support.\n\nperhaps?\n\n\n\n"},{"id":"554521","messageId":"xmqqzewoys2h.fsf@gitster.g","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-8-baf015c589c0@pks.im","subject":"Re: [PATCH 8/8] ci: drop redundant linux-reftable job","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-08T18:18:14Z","receivedAt":"2026-10-08T18:18:14Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n> The \"linux-reftable\" job exercises Git with reftables as its default\n> backend. But this job is arguably redundant because we already have the\n> \"linux-reftable-leaks\" job that exercises reftables with the leak\n> sanitizer enabled, and it is unlikely that we will catch any extra bugs\n> with the leak sanitizer disabled.\n>\n> Drop the job.\n>\n> Signed-off-by: Patrick Steinhardt <ps@pks.im>\n> ---\n>  .github/workflows/main.yml | 3 ---\n>  .gitlab-ci.yml             | 3 ---\n>  ci/run-build-and-tests.sh  | 2 +-\n>  3 files changed, 1 insertion(+), 7 deletions(-)\n\nAs linux-reftable-leaks job uses NO_{CVS,SVN,PR}_TESTS in ci/lib.sh\nto disable tests on these foreign-scm interoperability tests, this\nchange means reftable is no longer tested with them at all, no?\n\nNot that I personally see specific value in testing git-p4 with both\nreftable and reffiles backend, the loss of coverage needs to be\nnoted, if not justified, in the proposed commit log message.\n\nOther than that, nice thinking.\n\nThanks.\n\n"},{"id":"554553","messageId":"ash_zMOb47cFnvQO@pks.im","threadId":"66489","inReplyTo":"xmqqa4oo1313.fsf@gitster.g","subject":"Re: [PATCH 1/8] t5004: skip SHA-1-only test in SHA-256 repository","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-09T05:46:52Z","receivedAt":"2026-10-09T05:46:52Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Thu, Oct 08, 2026 at 11:05:28AM -0700, Junio C Hamano wrote:\n> Patrick Steinhardt <ps@pks.im> writes:\n> \n> > One of the tests in t5004 extracts a ZIP file that contains some objects\n> > larger than 4GB and then double-checks whether we can read and archive\n> > such an object. That test has a bunch of prerequities: it requires a 64\n> > bit `long`, unzip with 64-bit support and it only runs when EXPENSIVE is\n> > enabled. Consequently, not a lot of jobs even exercise this.\n> >\n> > One of the jobs that does run it though our Fedora-based job, as it\n> \n> \"One of the jobs that does run it though\" IS \"our Fedora-based job\"?\n\nOops, good catch.\n\nPatrick\n\n"},{"id":"554554","messageId":"ash_0TF-PG710XJS@pks.im","threadId":"66489","inReplyTo":"xmqq4iew12pw.fsf@gitster.g","subject":"Re: [PATCH 4/8] ci: switch away from unsupported i386/ubuntu image","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-09T05:46:57Z","receivedAt":"2026-10-09T05:46:57Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Thu, Oct 08, 2026 at 11:12:11AM -0700, Junio C Hamano wrote:\n> Todd Zullinger <tmz@pobox.com> writes:\n> \n> > Patrick Steinhardt wrote:\n> >> The linux32 job is used to exercise Git on a 32 bit platform. That job\n> >> uses i386/ubuntu:20.04 though, and that version of Ubuntu is end of life\n> >> nowadays. Furthermore, Ubuntu has dropped support for 32 bit entirely\n> >> with the 20.04 release, so we cannot easily upgrade it to a more recent\n> >> image anymore.\n> >\n> > Should \"with the 20.04 release\" be 22.04 (or whatever\n> > release dropped i386)?\n> \n> FWIW, I read the above to mean \"32bit support, together with 20.04,\n> are now gone\", and did not feel any need for rephrasing.  But\n> reading it again, yes, it can be read both ways.\n> \n>     Ubuntu has dropped support for 32-bit entirely, together with\n>     20.04 release, so upgrading it to a more recent image would not\n>     help us keeping 32-bit support.\n> \n> perhaps?\n\nI think that still reads a bit awkward. I've rewritten it to the\nfollowing:\n\n  The linux32 job is used to exercise Git on a 32 bit platform. That job\n  uses i386/ubuntu:20.04 though, and that version of Ubuntu is end of life\n  nowadays. Furthermore, Ubuntu 20.04 is the last release that has support\n  for 32 bit, so we cannot upgrade the image to a later version, either.\n\nPatrick\n\n"},{"id":"554555","messageId":"asiB25AareJgkKL5@pks.im","threadId":"66489","inReplyTo":"xmqqzewoys2h.fsf@gitster.g","subject":"Re: [PATCH 8/8] ci: drop redundant linux-reftable job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-09T05:55:39Z","receivedAt":"2026-10-09T05:55:39Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Thu, Oct 08, 2026 at 11:18:14AM -0700, Junio C Hamano wrote:\n> Patrick Steinhardt <ps@pks.im> writes:\n> \n> > The \"linux-reftable\" job exercises Git with reftables as its default\n> > backend. But this job is arguably redundant because we already have the\n> > \"linux-reftable-leaks\" job that exercises reftables with the leak\n> > sanitizer enabled, and it is unlikely that we will catch any extra bugs\n> > with the leak sanitizer disabled.\n> >\n> > Drop the job.\n> >\n> > Signed-off-by: Patrick Steinhardt <ps@pks.im>\n> > ---\n> >  .github/workflows/main.yml | 3 ---\n> >  .gitlab-ci.yml             | 3 ---\n> >  ci/run-build-and-tests.sh  | 2 +-\n> >  3 files changed, 1 insertion(+), 7 deletions(-)\n> \n> As linux-reftable-leaks job uses NO_{CVS,SVN,PR}_TESTS in ci/lib.sh\n> to disable tests on these foreign-scm interoperability tests, this\n> change means reftable is no longer tested with them at all, no?\n> \n> Not that I personally see specific value in testing git-p4 with both\n> reftable and reffiles backend, the loss of coverage needs to be\n> noted, if not justified, in the proposed commit log message.\n> \n> Other than that, nice thinking.\n\nHm, that's something I missed indeed. I don't really think that those\ntests are all that important, and I'd rather have all of these tools\nremoved from our code base anyway. But I find it hard to argue that we\nshould just drop test coverage for them altogether.\n\nSo how about arguing the other way round and making the job more useful?\nWe don't have good test coverage of reftables with SHA256, so we could\nadapt the job to exercise that combination.\n\nPatrick\n\n"},{"id":"554574","messageId":"20261009-pks-ci-housekeeping-v2-0-6863d58ef691@pks.im","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im","subject":"[PATCH v2 0/8] ci: some housekeeping and modernizations","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-09T11:31:57Z","receivedAt":"2026-10-09T11:31:57Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"Hi,\n\nthis patch series is a result from the discussions in [1]. It fixes a\ncouple of smaller issues in our CI and bumps jobs that use EOL Docker\nimages to instead use supported ones.\n\nPassing test runs can be found at [2] and [3] for GitLab and GitHub,\nrespectively.\n\nNote that I've also merged the Meson changes (ps/meson-improvements at\nce4a600322 (gitlab-ci: fix hanging MSVC jobs, 2026-09-24)) in there so\nthat GitLab passes, but those are not strictly required as a dependency.\n\nChanges in v2:\n  - Improve commit messages.\n  - Rework the \"linux-reftable\" job to be more useful instead of\n    dropping it.\n  - Link to v1: https://patch.msgid.link/20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im\n\nThanks!\n\nPatrick\n\n[1]: <20260906151137.GA328152@coredump.intra.peff.net>\n[2]: https://gitlab.com/gitlab-org/git/-/merge_requests/687\n[3]: https://github.com/git/git/pull/2445\n\n---\nPatrick Steinhardt (8):\n      t5004: skip SHA-1-only test in SHA-256 repository\n      ci: fix \"fedora-breaking-changes-meson\" job\n      ci: drop unused \"linux-clang\" logic\n      ci: switch away from unsupported i386/ubuntu image\n      ci: rename linux-TEST-vars job\n      ci: switch away from EOL'd Ubuntu version in linux-exotic\n      ci: drop now-dead Python 2 coverage\n      ci: improve reftable test coverage\n\n .github/workflows/main.yml      | 11 ++++-------\n .gitlab-ci.yml                  | 11 ++++-------\n ci/install-dependencies.sh      |  8 ++------\n ci/lib.sh                       | 13 ++-----------\n ci/run-build-and-tests.sh       | 14 +++++++-------\n t/t5004-archive-corner-cases.sh |  2 +-\n 6 files changed, 20 insertions(+), 39 deletions(-)\n\nRange-diff versus v1:\n\n1:  654fa99d33 ! 1:  61d0ab3180 t5004: skip SHA-1-only test in SHA-256 repository\n    @@ Commit message\n         bit `long`, unzip with 64-bit support and it only runs when EXPENSIVE is\n         enabled. Consequently, not a lot of jobs even exercise this.\n     \n    -    One of the jobs that does run it though our Fedora-based job, as it\n    +    One of the jobs that does run it though is our Fedora-based job, as it\n         ticks all the necessary boxes. But that job was silently broken: while\n         the intent was to run on Fedora with breaking changes enabled, they are\n         in fact disabled due to a typo.\n2:  c75705d4c3 = 2:  d3bef5a21e ci: fix \"fedora-breaking-changes-meson\" job\n3:  1d74ddf095 = 3:  e6d5135719 ci: drop unused \"linux-clang\" logic\n4:  8c1d17e976 ! 4:  21a32d6f33 ci: switch away from unsupported i386/ubuntu image\n    @@ Commit message\n     \n         The linux32 job is used to exercise Git on a 32 bit platform. That job\n         uses i386/ubuntu:20.04 though, and that version of Ubuntu is end of life\n    -    nowadays. Furthermore, Ubuntu has dropped support for 32 bit entirely\n    -    with the 20.04 release, so we cannot easily upgrade it to a more recent\n    -    image anymore.\n    +    nowadays. Furthermore, Ubuntu 20.04 is the last release that has support\n    +    for 32 bit, so we cannot upgrade the image to a later version, either.\n     \n         Switch the job over to use i386/debian instead. Note that starting with\n         Debian 13, support for i386 has been reduced [1]. But Debian still\n5:  4b919ad40e = 5:  01496b2238 ci: rename linux-TEST-vars job\n6:  ab371f734c = 6:  f248065fb5 ci: switch away from EOL'd Ubuntu version in linux-exotic\n7:  d0ff091832 = 7:  1148ebcab3 ci: drop now-dead Python 2 coverage\n8:  2b0df6d4a2 < -:  ---------- ci: drop redundant linux-reftable job\n-:  ---------- > 8:  71c2422b22 ci: improve reftable test coverage\n\n---\nbase-commit: 8e383dedc6bbc4fd7bbb203512fbf2eafc151e04\nchange-id: 20261008-pks-ci-housekeeping-4cf7fac3b0df\n\n\n"},{"id":"554575","messageId":"20261009-pks-ci-housekeeping-v2-1-6863d58ef691@pks.im","threadId":"66489","inReplyTo":"20261009-pks-ci-housekeeping-v2-0-6863d58ef691@pks.im","subject":"[PATCH v2 1/8] t5004: skip SHA-1-only test in SHA-256 repository","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-09T11:31:58Z","receivedAt":"2026-10-09T11:31:58Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"One of the tests in t5004 extracts a ZIP file that contains some objects\nlarger than 4GB and then double-checks whether we can read and archive\nsuch an object. That test has a bunch of prerequities: it requires a 64\nbit `long`, unzip with 64-bit support and it only runs when EXPENSIVE is\nenabled. Consequently, not a lot of jobs even exercise this.\n\nOne of the jobs that does run it though is our Fedora-based job, as it\nticks all the necessary boxes. But that job was silently broken: while\nthe intent was to run on Fedora with breaking changes enabled, they are\nin fact disabled due to a typo.\n\nWe're about to fix that typo in the next commit, but this will also\nuncover that the above test case is broken when running in SHA-256\nrepositories. The extracted objects are SHA-1 objects, so extracting\nthem into a SHA-256 repository is not going to yield anything good. So\nonce we fix the Fedora-based job to enable breaking changes, which will\nmake tests use SHA-256 by default, the test will break.\n\nFix this issue by adding the SHA1 prerequisite.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n t/t5004-archive-corner-cases.sh | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/t/t5004-archive-corner-cases.sh b/t/t5004-archive-corner-cases.sh\nindex 768b0ff85d..c9c879cc5f 100755\n--- a/t/t5004-archive-corner-cases.sh\n+++ b/t/t5004-archive-corner-cases.sh\n@@ -185,7 +185,7 @@ test_expect_success EXPENSIVE,UNZIP,UNZIP_ZIP64_SUPPORT \\\n \t\"$GIT_UNZIP\" -t many-big.zip\n '\n \n-test_expect_success EXPENSIVE,LONG_IS_64BIT,UNZIP,UNZIP_ZIP64_SUPPORT,ZIPINFO \\\n+test_expect_success EXPENSIVE,LONG_IS_64BIT,UNZIP,UNZIP_ZIP64_SUPPORT,ZIPINFO,SHA1 \\\n \t'zip archive with files bigger than 4GB' '\n \t# Pack created with:\n \t#   dd if=/dev/zero of=file bs=1M count=4100 && git hash-object -w file\n\n-- \n2.56.0.170.g584c36229d.dirty\n\n\n"},{"id":"554576","messageId":"20261009-pks-ci-housekeeping-v2-2-6863d58ef691@pks.im","threadId":"66489","inReplyTo":"20261009-pks-ci-housekeeping-v2-0-6863d58ef691@pks.im","subject":"[PATCH v2 2/8] ci: fix \"fedora-breaking-changes-meson\" job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-09T11:31:59Z","receivedAt":"2026-10-09T11:31:59Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"fedora-breaking-changes-meson\" job exercises Git with breaking\nchanges enabled on Fedora with Meson. There's a typo in our CI scripts\nthough, which has the effect that the build does not enable breaking\nchanges by accident.\n\nFix the typo.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n ci/run-build-and-tests.sh | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex 6a3b43b366..bc5058c917 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -18,7 +18,7 @@ almalinux-*|debian-*|fedora-*|linux-*)\n esac\n \n case \"$jobname\" in\n-fedora-breaking-changes-musl|linux-breaking-changes)\n+fedora-breaking-changes-meson|linux-breaking-changes)\n \texport WITH_BREAKING_CHANGES=YesPlease\n \tMESONFLAGS=\"$MESONFLAGS -Dbreaking_changes=true\"\n \t;;\n\n-- \n2.56.0.170.g584c36229d.dirty\n\n\n"},{"id":"554577","messageId":"20261009-pks-ci-housekeeping-v2-3-6863d58ef691@pks.im","threadId":"66489","inReplyTo":"20261009-pks-ci-housekeeping-v2-0-6863d58ef691@pks.im","subject":"[PATCH v2 3/8] ci: drop unused \"linux-clang\" logic","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-09T11:32:00Z","receivedAt":"2026-10-09T11:32:00Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"In d88d727143 (ci: drop linux-clang job, 2023-06-01) we have dropped the\n\"linux-clang\" job because another job already uses Clang anyway. But we\nforgot to also drop the logic in \"ci/run-build-and-tests.sh\", so we now\nhave some unused logic in there.\n\nDrop it.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n ci/run-build-and-tests.sh | 4 ----\n 1 file changed, 4 deletions(-)\n\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex bc5058c917..23e87cbbd6 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -37,10 +37,6 @@ linux-TEST-vars)\n \texport GIT_TEST_CHECKOUT_WORKERS=2\n \texport GIT_TEST_PACK_USE_BITMAP_BOUNDARY_TRAVERSAL=1\n \t;;\n-linux-clang)\n-\texport NO_RUST=UnfortunatelyYes\n-\texport GIT_TEST_DEFAULT_HASH=sha1\n-\t;;\n linux-sha256)\n \texport GIT_TEST_DEFAULT_HASH=sha256\n \t;;\n\n-- \n2.56.0.170.g584c36229d.dirty\n\n\n"},{"id":"554578","messageId":"20261009-pks-ci-housekeeping-v2-4-6863d58ef691@pks.im","threadId":"66489","inReplyTo":"20261009-pks-ci-housekeeping-v2-0-6863d58ef691@pks.im","subject":"[PATCH v2 4/8] ci: switch away from unsupported i386/ubuntu image","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-09T11:32:01Z","receivedAt":"2026-10-09T11:32:01Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The linux32 job is used to exercise Git on a 32 bit platform. That job\nuses i386/ubuntu:20.04 though, and that version of Ubuntu is end of life\nnowadays. Furthermore, Ubuntu 20.04 is the last release that has support\nfor 32 bit, so we cannot upgrade the image to a later version, either.\n\nSwitch the job over to use i386/debian instead. Note that starting with\nDebian 13, support for i386 has been reduced [1]. But Debian still\nreleases 32 bit Docker images for the latest release nowadays, so we\nwill have coverage until at least 2030.\n\n[1]: https://www.debian.org/releases/trixie/release-notes/issues.en.html#i386-reduced-support\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 3 +--\n .gitlab-ci.yml             | 3 +--\n ci/install-dependencies.sh | 6 +-----\n ci/lib.sh                  | 2 +-\n 4 files changed, 4 insertions(+), 10 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex b229739be8..6d1e37c8f1 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -431,9 +431,8 @@ jobs:\n           cc: gcc\n         - jobname: linux-musl-meson\n           image: alpine:latest\n-        # Supported until 2025-04-02.\n         - jobname: linux32\n-          image: i386/ubuntu:20.04\n+          image: i386/debian:latest\n         # A RHEL 8 compatible distro.  Supported until 2029-05-31.\n         - jobname: almalinux-8\n           image: almalinux:8\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 3f24835500..7d972f0c8b 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -65,9 +65,8 @@ test:linux:\n         CC: gcc\n       - jobname: linux-musl-meson\n         image: alpine:latest\n-        # Supported until 2025-04-02.\n       - jobname: linux32\n-        image: i386/ubuntu:20.04\n+        image: i386/debian:latest\n       # A RHEL 8 compatible distro.  Supported until 2029-05-31.\n       - jobname: almalinux-8\n         image: almalinux:8\ndiff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh\nindex d57dce5663..8783b48951 100755\n--- a/ci/install-dependencies.sh\n+++ b/ci/install-dependencies.sh\n@@ -39,7 +39,7 @@ fedora-*|almalinux-*)\n \tdnf -yq update >/dev/null &&\n \tdnf -yq install shadow-utils sudo make pkg-config gcc findutils diffutils perl python3 gawk gettext zlib-devel expat-devel openssl-devel curl-devel pcre2-devel $MESON_DEPS cargo >/dev/null\n \t;;\n-ubuntu-*|i386/ubuntu-*|debian-*)\n+ubuntu-*|i386/debian-*|debian-*)\n \t# Required so that apt doesn't wait for user input on certain packages.\n \texport DEBIAN_FRONTEND=noninteractive\n \n@@ -48,10 +48,6 @@ ubuntu-*|i386/ubuntu-*|debian-*)\n \t\tSVN='libsvn-perl subversion'\n \t\tLANGUAGES='language-pack-is'\n \t\t;;\n-\ti386/ubuntu-*)\n-\t\tSVN=\n-\t\tLANGUAGES='language-pack-is'\n-\t\t;;\n \t*)\n \t\tSVN='libsvn-perl subversion'\n \t\tLANGUAGES='locales-all'\ndiff --git a/ci/lib.sh b/ci/lib.sh\nindex c6ccbf8c17..d99e7b9da1 100755\n--- a/ci/lib.sh\n+++ b/ci/lib.sh\n@@ -262,7 +262,7 @@ then\n \t\tCI_OS_NAME=osx\n \t\tJOBS=$(nproc)\n \t\t;;\n-\t*,almalinux:*|*,alpine:*|*,debian:*|*,fedora:*|*,ubuntu:*|*,i386/ubuntu:*)\n+\t*,almalinux:*|*,alpine:*|*,debian:*|*,fedora:*|*,ubuntu:*|*,i386/debian:*)\n \t\tCI_OS_NAME=linux\n \t\tJOBS=$(nproc)\n \t\t;;\n\n-- \n2.56.0.170.g584c36229d.dirty\n\n\n"},{"id":"554579","messageId":"20261009-pks-ci-housekeeping-v2-5-6863d58ef691@pks.im","threadId":"66489","inReplyTo":"20261009-pks-ci-housekeeping-v2-0-6863d58ef691@pks.im","subject":"[PATCH v2 5/8] ci: rename linux-TEST-vars job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-09T11:32:02Z","receivedAt":"2026-10-09T11:32:02Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"linux-TEST-vars\" job exercises Git with a bunch of non-default\noptions enabled. The name of that job makes you want to cry though due\nto the weird upper-casing and because it doesn't really tell you what it\neven intends to do.\n\nRename the job to \"linux-exotic\" instead.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 2 +-\n .gitlab-ci.yml             | 2 +-\n ci/run-build-and-tests.sh  | 2 +-\n 3 files changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex 6d1e37c8f1..d7a301ec98 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -408,7 +408,7 @@ jobs:\n         - jobname: linux-reftable\n           image: ubuntu:rolling\n           cc: clang\n-        - jobname: linux-TEST-vars\n+        - jobname: linux-exotic\n           image: ubuntu:20.04\n           cc: gcc\n           cc_package: gcc-8\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 7d972f0c8b..27a16ed086 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -42,7 +42,7 @@ test:linux:\n       - jobname: linux-reftable\n         image: ubuntu:rolling\n         CC: clang\n-      - jobname: linux-TEST-vars\n+      - jobname: linux-exotic\n         image: ubuntu:20.04\n         CC: gcc\n         CC_PACKAGE: gcc-8\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex 23e87cbbd6..9381ff8893 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -22,7 +22,7 @@ fedora-breaking-changes-meson|linux-breaking-changes)\n \texport WITH_BREAKING_CHANGES=YesPlease\n \tMESONFLAGS=\"$MESONFLAGS -Dbreaking_changes=true\"\n \t;;\n-linux-TEST-vars)\n+linux-exotic)\n \texport OPENSSL_SHA1_UNSAFE=YesPlease\n \texport GIT_TEST_SPLIT_INDEX=yes\n \texport GIT_TEST_FULL_IN_PACK_ARRAY=true\n\n-- \n2.56.0.170.g584c36229d.dirty\n\n\n"},{"id":"554580","messageId":"20261009-pks-ci-housekeeping-v2-6-6863d58ef691@pks.im","threadId":"66489","inReplyTo":"20261009-pks-ci-housekeeping-v2-0-6863d58ef691@pks.im","subject":"[PATCH v2 6/8] ci: switch away from EOL'd Ubuntu version in linux-exotic","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-09T11:32:03Z","receivedAt":"2026-10-09T11:32:03Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"linux-exotic\" job still uses Ubuntu 20.04, which is end of life\nnowadays and starting to show some cracks. Switch it over to use the\n\"latest\" tag instead so that we don't have to constantly update it\nanymore.\n\nNow arguably, this reduces test coverage for old versions of Ubuntu.\nBut \"latest\" at least points to the most up-to-date LTS release of\nUbuntu, compared to the \"rolling\" tag that uses the latest release\nregardless of the LTS status. So while \"latest\" and \"rolling\" are the\nsame right now, that's not always the case.\n\nFurthermore, we have other jobs that test with ancient versions of\nLinux, like for example the one that uses AlmaLinux 8 (2021, originally\ntracking RHEL 8 from 2019) or Debian 12 (2023).\n\nNote that this also requires us to switch away from GCC 8, which is not\nsupported by Ubuntu 26.04 anymore. Instead we simply use the default\nversion of GCC.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 4 +---\n .gitlab-ci.yml             | 4 +---\n 2 files changed, 2 insertions(+), 6 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex d7a301ec98..5b772dab55 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -409,9 +409,7 @@ jobs:\n           image: ubuntu:rolling\n           cc: clang\n         - jobname: linux-exotic\n-          image: ubuntu:20.04\n-          cc: gcc\n-          cc_package: gcc-8\n+          image: ubuntu:latest\n         - jobname: linux-breaking-changes\n           cc: gcc\n           image: ubuntu:rolling\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 27a16ed086..de40434ae3 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -43,9 +43,7 @@ test:linux:\n         image: ubuntu:rolling\n         CC: clang\n       - jobname: linux-exotic\n-        image: ubuntu:20.04\n-        CC: gcc\n-        CC_PACKAGE: gcc-8\n+        image: ubuntu:latest\n       - jobname: linux-breaking-changes\n         image: ubuntu:rolling\n         CC: gcc\n\n-- \n2.56.0.170.g584c36229d.dirty\n\n\n"},{"id":"554581","messageId":"20261009-pks-ci-housekeeping-v2-7-6863d58ef691@pks.im","threadId":"66489","inReplyTo":"20261009-pks-ci-housekeeping-v2-0-6863d58ef691@pks.im","subject":"[PATCH v2 7/8] ci: drop now-dead Python 2 coverage","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-09T11:32:04Z","receivedAt":"2026-10-09T11:32:04Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"In the preceding commit we've dropped the last job that still used\nUbuntu 20.04. We still had some conditional logic for that specific\nimage that made us use Python 2 instead of Python 3, but this is dead\ncode now.\n\nWe could of course exercise Python 2 in any of our other CI jobs. But it\nreached end of life in 2020 already, and none of the distros that we use\nhave it packaged anymore. Furthermore, it seems like the world has\nfinally adapted to Python 3. So it doesn't feel all that useful to still\nexercise it.\n\nDrop the logic and instead use Python 3 unconditionally.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n ci/install-dependencies.sh |  2 +-\n ci/lib.sh                  | 11 +----------\n 2 files changed, 2 insertions(+), 11 deletions(-)\n\ndiff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh\nindex 8783b48951..4b1733ad15 100755\n--- a/ci/install-dependencies.sh\n+++ b/ci/install-dependencies.sh\n@@ -61,7 +61,7 @@ ubuntu-*|i386/debian-*|debian-*)\n \t\ttcl tk gettext zlib1g-dev perl-modules liberror-perl libauthen-sasl-perl \\\n \t\tlibemail-valid-perl libio-pty-perl libio-socket-ssl-perl libnet-smtp-ssl-perl libdbd-sqlite3-perl libcgi-pm-perl \\\n \t\tlibsecret-1-dev libpcre2-dev meson ninja-build pkg-config cargo \\\n-\t\t${CC_PACKAGE:-${CC:-gcc}} $PYTHON_PACKAGE\n+\t\t${CC_PACKAGE:-${CC:-gcc}} python3\n \n \t# Starting with Ubuntu 25.10, sudo can now be provided via either\n \t# sudo(1) or sudo-rs(1), with the latter being the default. The problem\ndiff --git a/ci/lib.sh b/ci/lib.sh\nindex d99e7b9da1..3ec10488d4 100755\n--- a/ci/lib.sh\n+++ b/ci/lib.sh\n@@ -335,16 +335,7 @@ esac\n \n case \"$distro\" in\n ubuntu-*)\n-\t# Python 2 is end of life, and Ubuntu 23.04 and newer don't actually\n-\t# have it anymore. We thus only test with Python 2 on older LTS\n-\t# releases.\n-\tif test \"$distro\" = \"ubuntu-20.04\"\n-\tthen\n-\t\tPYTHON_PACKAGE=python2\n-\telse\n-\t\tPYTHON_PACKAGE=python3\n-\tfi\n-\tMAKEFLAGS=\"$MAKEFLAGS PYTHON_PATH=/usr/bin/$PYTHON_PACKAGE\"\n+\tMAKEFLAGS=\"$MAKEFLAGS PYTHON_PATH=/usr/bin/python3\"\n \n \texport GIT_TEST_HTTPD=true\n \n\n-- \n2.56.0.170.g584c36229d.dirty\n\n\n"},{"id":"554582","messageId":"20261009-pks-ci-housekeeping-v2-8-6863d58ef691@pks.im","threadId":"66489","inReplyTo":"20261009-pks-ci-housekeeping-v2-0-6863d58ef691@pks.im","subject":"[PATCH v2 8/8] ci: improve reftable test coverage","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-09T11:32:05Z","receivedAt":"2026-10-09T11:32:05Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"linux-reftable\" job exercises Git with reftables as its default\nbackend. But this job is arguably redundant because we already have the\n\"linux-reftable-leaks\" job that exercises reftables with the leak\nsanitizer enabled, and it is unlikely that we will catch any extra bugs\nwith the leak sanitizer disabled.\n\nOne may thus be triggered to just drop the \"linux-reftable\" job in favor\nof the leak-checking variant. But the latter disables a couple of other\ntests that exercise git-p4, git-svn and other tools. Those tools may not\nbe an essential part of Git nowadays, but I don't quite feel comfortable\nwith reducing test coverage.\n\nInstead, adapt the job to run reftables together with SHA256. which is\nan area that we don't have test coverage for.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 2 +-\n .gitlab-ci.yml             | 2 +-\n ci/run-build-and-tests.sh  | 6 +++++-\n 3 files changed, 7 insertions(+), 3 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex 5b772dab55..0939833e57 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -405,7 +405,7 @@ jobs:\n         - jobname: linux-sha256\n           image: ubuntu:rolling\n           cc: clang\n-        - jobname: linux-reftable\n+        - jobname: linux-reftable-sha256\n           image: ubuntu:rolling\n           cc: clang\n         - jobname: linux-exotic\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex de40434ae3..b814963ff7 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -39,7 +39,7 @@ test:linux:\n       - jobname: linux-sha256\n         image: ubuntu:rolling\n         CC: clang\n-      - jobname: linux-reftable\n+      - jobname: linux-reftable-sha256\n         image: ubuntu:rolling\n         CC: clang\n       - jobname: linux-exotic\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex 9381ff8893..c6e61d5794 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -40,7 +40,11 @@ linux-exotic)\n linux-sha256)\n \texport GIT_TEST_DEFAULT_HASH=sha256\n \t;;\n-linux-reftable|linux-reftable-leaks|osx-reftable)\n+linux-reftable-sha256)\n+\texport GIT_TEST_DEFAULT_HASH=sha256\n+\texport GIT_TEST_DEFAULT_REF_STORAGE_FORMAT=reftable\n+\t;;\n+linux-reftable-leaks|osx-reftable)\n \texport GIT_TEST_DEFAULT_REF_STORAGE_FORMAT=reftable\n \t;;\n \n\n-- \n2.56.0.170.g584c36229d.dirty\n\n\n"},{"id":"554618","messageId":"askI1DGldZx8ElIN@szeder.dev","threadId":"66489","inReplyTo":"20261009-pks-ci-housekeeping-v2-5-6863d58ef691@pks.im","subject":"Re: [PATCH v2 5/8] ci: rename linux-TEST-vars job","fromName":"SZEDER Gábor","fromEmail":"szeder.dev@gmail.com","sentAt":"2026-10-09T15:31:32Z","receivedAt":"2026-10-09T15:31:32Z","isPatch":true,"sender":{"key":"szeder.dev@gmail.com","avatar":"https://avatars.githubusercontent.com/u/116324?v=4"},"body":"On Fri, Oct 09, 2026 at 01:32:02PM +0200, Patrick Steinhardt wrote:\n> The \"linux-TEST-vars\" job exercises Git with a bunch of non-default\n> options enabled. The name of that job makes you want to cry though due\n> to the weird upper-casing\n\nYeah, it's an eyesore indeed.\n\n> and because it doesn't really tell you what it\n> even intends to do.\n\nIt intends to set a bunch of GIT_TEST_* variables, and since it has\ntest vars in its name, I'd say that it does a decent job at conveying\nits intentions.\n\n> Rename the job to \"linux-exotic\" instead.\n\nSeeing \"linux-exotic\", I would think of a job running tests on an\nexotic Linux distro, or on an exotic platform...  but it wouldn't\noccur to me that it intends to set a bunch of GIT_TEST_* variables,\nsimply because there is nothing in its name to indicate that.\n\nI think this patch makes things worse.\n\n\n"},{"id":"554657","messageId":"xmqq7bjqoc8j.fsf@gitster.g","threadId":"66489","inReplyTo":"asiB25AareJgkKL5@pks.im","subject":"Re: [PATCH 8/8] ci: drop redundant linux-reftable job","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-09T20:22:36Z","receivedAt":"2026-10-09T20:22:36Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n> So how about arguing the other way round and making the job more useful?\n> We don't have good test coverage of reftables with SHA256, so we could\n> adapt the job to exercise that combination.\n\nYeah, instead of doing sha1 and leaks, doing sha1 and sha256 would\nbe much more useful ;-).\n\n"},{"id":"554830","messageId":"as3b-u7SzE3uPwQx@pks.im","threadId":"66489","inReplyTo":"askI1DGldZx8ElIN@szeder.dev","subject":"Re: [PATCH v2 5/8] ci: rename linux-TEST-vars job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-13T07:21:30Z","receivedAt":"2026-10-13T07:21:30Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Fri, Oct 09, 2026 at 05:31:32PM +0200, SZEDER Gábor wrote:\n> On Fri, Oct 09, 2026 at 01:32:02PM +0200, Patrick Steinhardt wrote:\n> > The \"linux-TEST-vars\" job exercises Git with a bunch of non-default\n> > options enabled. The name of that job makes you want to cry though due\n> > to the weird upper-casing\n> \n> Yeah, it's an eyesore indeed.\n> \n> > and because it doesn't really tell you what it\n> > even intends to do.\n> \n> It intends to set a bunch of GIT_TEST_* variables, and since it has\n> test vars in its name, I'd say that it does a decent job at conveying\n> its intentions.\n\nThat only tells you anything in case you evne know about the GIT_TEST\nvariariables, but doesn't really give you much of an idea what the\nintent of that job is. But...\n\n> > Rename the job to \"linux-exotic\" instead.\n> \n> Seeing \"linux-exotic\", I would think of a job running tests on an\n> exotic Linux distro, or on an exotic platform...  but it wouldn't\n> occur to me that it intends to set a bunch of GIT_TEST_* variables,\n> simply because there is nothing in its name to indicate that.\n> \n> I think this patch makes things worse.\n\n... I think it's still a fair point. The question is whether we can come\nup with a better name then that is not an eyesore and that gives you a\nclue what the job is doing without you having to know about the\nunderlying mechanism.\n\nA couple of names that come to my mind would be \"linux-nondefault\",\n\"linux-optional-features\"... and not much else. Do you have any\nsuggestions?\n\nThanks!\n\nPatrick\n\n"},{"id":"554868","messageId":"xmqq33u91wu0.fsf@gitster.g","threadId":"66489","inReplyTo":"as3b-u7SzE3uPwQx@pks.im","subject":"Re: [PATCH v2 5/8] ci: rename linux-TEST-vars job","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-13T14:47:35Z","receivedAt":"2026-10-13T14:47:35Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n>> Seeing \"linux-exotic\", I would think of a job running tests on an\n>> exotic Linux distro, or on an exotic platform...  but it wouldn't\n>> occur to me that it intends to set a bunch of GIT_TEST_* variables,\n>> simply because there is nothing in its name to indicate that.\n>> \n>> I think this patch makes things worse.\n>\n> ... I think it's still a fair point. The question is whether we can come\n> up with a better name then that is not an eyesore and that gives you a\n> clue what the job is doing without you having to know about the\n> underlying mechanism.\n>\n> A couple of names that come to my mind would be \"linux-nondefault\",\n> \"linux-optional-features\"... and not much else. Do you have any\n> suggestions?\n\nAmong the following, my current favourite is \"feathre testbed\".\n\n== Feature & Capability Focus ==\n\n* linux-experimental-features / linux-experimental\n\n  Directly states that the job enables experimental features.  This\n  is clear, standard industry terminology, and avoids any ambiguity\n  about the Linux distribution itself.\n\n* linux-feature-testbed\n\n  Positions the job as a testbed specifically for experimental\n  features, which aligns perfectly with its testing nature.\n\n* linux-exotic-features\n\n  Keeps the \"exotic\" keyword you proposed but qualifies it with\n  \"features\", immediately removing the risk of sounding like an\n  exotic Linux distribution.\n\n== Build & Configuration Focus ==\n\n* linux-nondefault / linux-nonstandard\n\n  A build that departs from the standard, out-of-the-box\n  configuration.\n\n* linux-extra-knobs\n\n  Uses Git-centric terminology.  Since you customize build-time\n  configuration knobs to enable these experimental features, this is\n  highly descriptive and intuitive for developers.\n\n* linux-super-tweaked / linux-highly-tweaked\n\n  Emphasizes that the build variables have been heavily customized.\n\n* linux-custom-vars\n\n  A direct, no-nonsense replacement for 'linux-TEST-vars' that\n  clarifies that the variables are custom/customized rather than\n  just \"test\" variables.\n\n== Testing & Robustness Focus ==\n\n* linux-stress-features\n\n  Implies that we are stretching the capabilities of the build by\n  turning on non-standard configurations.\n\n* linux-edge-cases\n\n  Focuses on the goal of the job: testing edge cases enabled by\n  experimental configuration variables.\n\n* linux-all-features\n\n  If the experimental variables essentially turn on all optional\n  features, this is a very clean and positive name.\nk\n\n"},{"id":"554954","messageId":"as8pKXTBC33_iQxu@pks.im","threadId":"66489","inReplyTo":"xmqq33u91wu0.fsf@gitster.g","subject":"Re: [PATCH v2 5/8] ci: rename linux-TEST-vars job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T07:03:05Z","receivedAt":"2026-10-14T07:03:05Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Tue, Oct 13, 2026 at 07:47:35AM -0700, Junio C Hamano wrote:\n> Patrick Steinhardt <ps@pks.im> writes:\n> \n> >> Seeing \"linux-exotic\", I would think of a job running tests on an\n> >> exotic Linux distro, or on an exotic platform...  but it wouldn't\n> >> occur to me that it intends to set a bunch of GIT_TEST_* variables,\n> >> simply because there is nothing in its name to indicate that.\n> >> \n> >> I think this patch makes things worse.\n> >\n> > ... I think it's still a fair point. The question is whether we can come\n> > up with a better name then that is not an eyesore and that gives you a\n> > clue what the job is doing without you having to know about the\n> > underlying mechanism.\n> >\n> > A couple of names that come to my mind would be \"linux-nondefault\",\n> > \"linux-optional-features\"... and not much else. Do you have any\n> > suggestions?\n> \n> Among the following, my current favourite is \"feathre testbed\".\n> \n> == Feature & Capability Focus ==\n> \n> * linux-experimental-features / linux-experimental\n> \n>   Directly states that the job enables experimental features.  This\n>   is clear, standard industry terminology, and avoids any ambiguity\n>   about the Linux distribution itself.\n\nNot all of the features are experimental though, so I feel like this is\na bit misleading.\n\n> * linux-feature-testbed\n> \n>   Positions the job as a testbed specifically for experimental\n>   features, which aligns perfectly with its testing nature.\n\nI like this one, will adopt the naming. Thanks!\n\nPatrick\n\n"},{"id":"554964","messageId":"20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im","subject":"[PATCH v3 0/8] ci: some housekeeping and modernizations","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T08:30:26Z","receivedAt":"2026-10-14T08:30:26Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"Hi,\n\nthis patch series is a result from the discussions in [1]. It fixes a\ncouple of smaller issues in our CI and bumps jobs that use EOL Docker\nimages to instead use supported ones.\n\nPassing test runs can be found at [2] and [3] for GitLab and GitHub,\nrespectively.\n\nNote that I've also merged the Meson changes (ps/meson-improvements at\nce4a600322 (gitlab-ci: fix hanging MSVC jobs, 2026-09-24)) in there so\nthat GitLab passes, but those are not strictly required as a dependency.\n\nChanges in v2:\n  - Improve commit messages.\n  - Rework the \"linux-reftable\" job to be more useful instead of\n    dropping it.\n  - Rename \"linux-exotic\" to \"linux-feature-testbed\".\n  - Link to v1: https://patch.msgid.link/20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im\n\nThanks!\n\nPatrick\n\n[1]: <20260906151137.GA328152@coredump.intra.peff.net>\n[2]: https://gitlab.com/gitlab-org/git/-/merge_requests/687\n[3]: https://github.com/git/git/pull/2445\n\n---\nPatrick Steinhardt (8):\n      t5004: skip SHA-1-only test in SHA-256 repository\n      ci: fix \"fedora-breaking-changes-meson\" job\n      ci: drop unused \"linux-clang\" logic\n      ci: switch away from unsupported i386/ubuntu image\n      ci: rename linux-TEST-vars job\n      ci: switch away from EOL'd Ubuntu version in linux-feature-testbed\n      ci: drop now-dead Python 2 coverage\n      ci: improve reftable test coverage\n\n .github/workflows/main.yml      | 11 ++++-------\n .gitlab-ci.yml                  | 11 ++++-------\n ci/install-dependencies.sh      |  8 ++------\n ci/lib.sh                       | 13 ++-----------\n ci/run-build-and-tests.sh       | 14 +++++++-------\n t/t5004-archive-corner-cases.sh |  2 +-\n 6 files changed, 20 insertions(+), 39 deletions(-)\n\nRange-diff versus v2:\n\n1:  6bf6c0285e = 1:  f000630dda t5004: skip SHA-1-only test in SHA-256 repository\n2:  ad57a87914 = 2:  93fce3a349 ci: fix \"fedora-breaking-changes-meson\" job\n3:  7f80b65aed = 3:  a79409be82 ci: drop unused \"linux-clang\" logic\n4:  1e2dfbc1b1 = 4:  7566046967 ci: switch away from unsupported i386/ubuntu image\n5:  e2e71b0760 ! 5:  b6117e4ed7 ci: rename linux-TEST-vars job\n    @@ Commit message\n         to the weird upper-casing and because it doesn't really tell you what it\n         even intends to do.\n     \n    -    Rename the job to \"linux-exotic\" instead.\n    +    Rename the job to \"linux-feature-testbed\" instead.\n     \n    +    Helped-by: Junio C Hamano <gitster@pobox.com>\n         Signed-off-by: Patrick Steinhardt <ps@pks.im>\n     \n      ## .github/workflows/main.yml ##\n    @@ .github/workflows/main.yml: jobs:\n                image: ubuntu:rolling\n                cc: clang\n     -        - jobname: linux-TEST-vars\n    -+        - jobname: linux-exotic\n    ++        - jobname: linux-feature-testbed\n                image: ubuntu:20.04\n                cc: gcc\n                cc_package: gcc-8\n    @@ .gitlab-ci.yml: test:linux:\n              image: ubuntu:rolling\n              CC: clang\n     -      - jobname: linux-TEST-vars\n    -+      - jobname: linux-exotic\n    ++      - jobname: linux-feature-testbed\n              image: ubuntu:20.04\n              CC: gcc\n              CC_PACKAGE: gcc-8\n    @@ ci/run-build-and-tests.sh: fedora-breaking-changes-meson|linux-breaking-changes)\n      \tMESONFLAGS=\"$MESONFLAGS -Dbreaking_changes=true\"\n      \t;;\n     -linux-TEST-vars)\n    -+linux-exotic)\n    ++linux-feature-testbed)\n      \texport OPENSSL_SHA1_UNSAFE=YesPlease\n      \texport GIT_TEST_SPLIT_INDEX=yes\n      \texport GIT_TEST_FULL_IN_PACK_ARRAY=true\n6:  0a83a736af ! 6:  e434629907 ci: switch away from EOL'd Ubuntu version in linux-exotic\n    @@ Metadata\n     Author: Patrick Steinhardt <ps@pks.im>\n     \n      ## Commit message ##\n    -    ci: switch away from EOL'd Ubuntu version in linux-exotic\n    +    ci: switch away from EOL'd Ubuntu version in linux-feature-testbed\n     \n    -    The \"linux-exotic\" job still uses Ubuntu 20.04, which is end of life\n    -    nowadays and starting to show some cracks. Switch it over to use the\n    -    \"latest\" tag instead so that we don't have to constantly update it\n    +    The \"linux-feature-testbed\" job still uses Ubuntu 20.04, which is end of\n    +    life nowadays and starting to show some cracks. Switch it over to use\n    +    the \"latest\" tag instead so that we don't have to constantly update it\n         anymore.\n     \n         Now arguably, this reduces test coverage for old versions of Ubuntu.\n    @@ .github/workflows/main.yml\n     @@ .github/workflows/main.yml: jobs:\n                image: ubuntu:rolling\n                cc: clang\n    -         - jobname: linux-exotic\n    +         - jobname: linux-feature-testbed\n     -          image: ubuntu:20.04\n     -          cc: gcc\n     -          cc_package: gcc-8\n    @@ .gitlab-ci.yml\n     @@ .gitlab-ci.yml: test:linux:\n              image: ubuntu:rolling\n              CC: clang\n    -       - jobname: linux-exotic\n    +       - jobname: linux-feature-testbed\n     -        image: ubuntu:20.04\n     -        CC: gcc\n     -        CC_PACKAGE: gcc-8\n7:  9f7b154520 = 7:  72736847d4 ci: drop now-dead Python 2 coverage\n8:  d97f36f5f9 ! 8:  fc15ae0fcc ci: improve reftable test coverage\n    @@ .github/workflows/main.yml: jobs:\n     +        - jobname: linux-reftable-sha256\n                image: ubuntu:rolling\n                cc: clang\n    -         - jobname: linux-exotic\n    +         - jobname: linux-feature-testbed\n     \n      ## .gitlab-ci.yml ##\n     @@ .gitlab-ci.yml: test:linux:\n    @@ .gitlab-ci.yml: test:linux:\n     +      - jobname: linux-reftable-sha256\n              image: ubuntu:rolling\n              CC: clang\n    -       - jobname: linux-exotic\n    +       - jobname: linux-feature-testbed\n     \n      ## ci/run-build-and-tests.sh ##\n    -@@ ci/run-build-and-tests.sh: linux-exotic)\n    +@@ ci/run-build-and-tests.sh: linux-feature-testbed)\n      linux-sha256)\n      \texport GIT_TEST_DEFAULT_HASH=sha256\n      \t;;\n\n---\nbase-commit: 8e383dedc6bbc4fd7bbb203512fbf2eafc151e04\nchange-id: 20261008-pks-ci-housekeeping-4cf7fac3b0df\n\n\n"},{"id":"554965","messageId":"20261014-pks-ci-housekeeping-v3-1-04c24e1f480d@pks.im","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im","subject":"[PATCH v3 1/8] t5004: skip SHA-1-only test in SHA-256 repository","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T08:30:27Z","receivedAt":"2026-10-14T08:30:27Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"One of the tests in t5004 extracts a ZIP file that contains some objects\nlarger than 4GB and then double-checks whether we can read and archive\nsuch an object. That test has a bunch of prerequities: it requires a 64\nbit `long`, unzip with 64-bit support and it only runs when EXPENSIVE is\nenabled. Consequently, not a lot of jobs even exercise this.\n\nOne of the jobs that does run it though is our Fedora-based job, as it\nticks all the necessary boxes. But that job was silently broken: while\nthe intent was to run on Fedora with breaking changes enabled, they are\nin fact disabled due to a typo.\n\nWe're about to fix that typo in the next commit, but this will also\nuncover that the above test case is broken when running in SHA-256\nrepositories. The extracted objects are SHA-1 objects, so extracting\nthem into a SHA-256 repository is not going to yield anything good. So\nonce we fix the Fedora-based job to enable breaking changes, which will\nmake tests use SHA-256 by default, the test will break.\n\nFix this issue by adding the SHA1 prerequisite.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n t/t5004-archive-corner-cases.sh | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/t/t5004-archive-corner-cases.sh b/t/t5004-archive-corner-cases.sh\nindex 768b0ff85d..c9c879cc5f 100755\n--- a/t/t5004-archive-corner-cases.sh\n+++ b/t/t5004-archive-corner-cases.sh\n@@ -185,7 +185,7 @@ test_expect_success EXPENSIVE,UNZIP,UNZIP_ZIP64_SUPPORT \\\n \t\"$GIT_UNZIP\" -t many-big.zip\n '\n \n-test_expect_success EXPENSIVE,LONG_IS_64BIT,UNZIP,UNZIP_ZIP64_SUPPORT,ZIPINFO \\\n+test_expect_success EXPENSIVE,LONG_IS_64BIT,UNZIP,UNZIP_ZIP64_SUPPORT,ZIPINFO,SHA1 \\\n \t'zip archive with files bigger than 4GB' '\n \t# Pack created with:\n \t#   dd if=/dev/zero of=file bs=1M count=4100 && git hash-object -w file\n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"554966","messageId":"20261014-pks-ci-housekeeping-v3-2-04c24e1f480d@pks.im","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im","subject":"[PATCH v3 2/8] ci: fix \"fedora-breaking-changes-meson\" job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T08:30:28Z","receivedAt":"2026-10-14T08:30:28Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"fedora-breaking-changes-meson\" job exercises Git with breaking\nchanges enabled on Fedora with Meson. There's a typo in our CI scripts\nthough, which has the effect that the build does not enable breaking\nchanges by accident.\n\nFix the typo.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n ci/run-build-and-tests.sh | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex 6a3b43b366..bc5058c917 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -18,7 +18,7 @@ almalinux-*|debian-*|fedora-*|linux-*)\n esac\n \n case \"$jobname\" in\n-fedora-breaking-changes-musl|linux-breaking-changes)\n+fedora-breaking-changes-meson|linux-breaking-changes)\n \texport WITH_BREAKING_CHANGES=YesPlease\n \tMESONFLAGS=\"$MESONFLAGS -Dbreaking_changes=true\"\n \t;;\n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"554967","messageId":"20261014-pks-ci-housekeeping-v3-3-04c24e1f480d@pks.im","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im","subject":"[PATCH v3 3/8] ci: drop unused \"linux-clang\" logic","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T08:30:29Z","receivedAt":"2026-10-14T08:30:29Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"In d88d727143 (ci: drop linux-clang job, 2023-06-01) we have dropped the\n\"linux-clang\" job because another job already uses Clang anyway. But we\nforgot to also drop the logic in \"ci/run-build-and-tests.sh\", so we now\nhave some unused logic in there.\n\nDrop it.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n ci/run-build-and-tests.sh | 4 ----\n 1 file changed, 4 deletions(-)\n\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex bc5058c917..23e87cbbd6 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -37,10 +37,6 @@ linux-TEST-vars)\n \texport GIT_TEST_CHECKOUT_WORKERS=2\n \texport GIT_TEST_PACK_USE_BITMAP_BOUNDARY_TRAVERSAL=1\n \t;;\n-linux-clang)\n-\texport NO_RUST=UnfortunatelyYes\n-\texport GIT_TEST_DEFAULT_HASH=sha1\n-\t;;\n linux-sha256)\n \texport GIT_TEST_DEFAULT_HASH=sha256\n \t;;\n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"554968","messageId":"20261014-pks-ci-housekeeping-v3-4-04c24e1f480d@pks.im","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im","subject":"[PATCH v3 4/8] ci: switch away from unsupported i386/ubuntu image","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T08:30:30Z","receivedAt":"2026-10-14T08:30:30Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The linux32 job is used to exercise Git on a 32 bit platform. That job\nuses i386/ubuntu:20.04 though, and that version of Ubuntu is end of life\nnowadays. Furthermore, Ubuntu 20.04 is the last release that has support\nfor 32 bit, so we cannot upgrade the image to a later version, either.\n\nSwitch the job over to use i386/debian instead. Note that starting with\nDebian 13, support for i386 has been reduced [1]. But Debian still\nreleases 32 bit Docker images for the latest release nowadays, so we\nwill have coverage until at least 2030.\n\n[1]: https://www.debian.org/releases/trixie/release-notes/issues.en.html#i386-reduced-support\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 3 +--\n .gitlab-ci.yml             | 3 +--\n ci/install-dependencies.sh | 6 +-----\n ci/lib.sh                  | 2 +-\n 4 files changed, 4 insertions(+), 10 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex b229739be8..6d1e37c8f1 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -431,9 +431,8 @@ jobs:\n           cc: gcc\n         - jobname: linux-musl-meson\n           image: alpine:latest\n-        # Supported until 2025-04-02.\n         - jobname: linux32\n-          image: i386/ubuntu:20.04\n+          image: i386/debian:latest\n         # A RHEL 8 compatible distro.  Supported until 2029-05-31.\n         - jobname: almalinux-8\n           image: almalinux:8\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 3f24835500..7d972f0c8b 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -65,9 +65,8 @@ test:linux:\n         CC: gcc\n       - jobname: linux-musl-meson\n         image: alpine:latest\n-        # Supported until 2025-04-02.\n       - jobname: linux32\n-        image: i386/ubuntu:20.04\n+        image: i386/debian:latest\n       # A RHEL 8 compatible distro.  Supported until 2029-05-31.\n       - jobname: almalinux-8\n         image: almalinux:8\ndiff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh\nindex d57dce5663..8783b48951 100755\n--- a/ci/install-dependencies.sh\n+++ b/ci/install-dependencies.sh\n@@ -39,7 +39,7 @@ fedora-*|almalinux-*)\n \tdnf -yq update >/dev/null &&\n \tdnf -yq install shadow-utils sudo make pkg-config gcc findutils diffutils perl python3 gawk gettext zlib-devel expat-devel openssl-devel curl-devel pcre2-devel $MESON_DEPS cargo >/dev/null\n \t;;\n-ubuntu-*|i386/ubuntu-*|debian-*)\n+ubuntu-*|i386/debian-*|debian-*)\n \t# Required so that apt doesn't wait for user input on certain packages.\n \texport DEBIAN_FRONTEND=noninteractive\n \n@@ -48,10 +48,6 @@ ubuntu-*|i386/ubuntu-*|debian-*)\n \t\tSVN='libsvn-perl subversion'\n \t\tLANGUAGES='language-pack-is'\n \t\t;;\n-\ti386/ubuntu-*)\n-\t\tSVN=\n-\t\tLANGUAGES='language-pack-is'\n-\t\t;;\n \t*)\n \t\tSVN='libsvn-perl subversion'\n \t\tLANGUAGES='locales-all'\ndiff --git a/ci/lib.sh b/ci/lib.sh\nindex c6ccbf8c17..d99e7b9da1 100755\n--- a/ci/lib.sh\n+++ b/ci/lib.sh\n@@ -262,7 +262,7 @@ then\n \t\tCI_OS_NAME=osx\n \t\tJOBS=$(nproc)\n \t\t;;\n-\t*,almalinux:*|*,alpine:*|*,debian:*|*,fedora:*|*,ubuntu:*|*,i386/ubuntu:*)\n+\t*,almalinux:*|*,alpine:*|*,debian:*|*,fedora:*|*,ubuntu:*|*,i386/debian:*)\n \t\tCI_OS_NAME=linux\n \t\tJOBS=$(nproc)\n \t\t;;\n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"554969","messageId":"20261014-pks-ci-housekeeping-v3-5-04c24e1f480d@pks.im","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im","subject":"[PATCH v3 5/8] ci: rename linux-TEST-vars job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T08:30:31Z","receivedAt":"2026-10-14T08:30:31Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"linux-TEST-vars\" job exercises Git with a bunch of non-default\noptions enabled. The name of that job makes you want to cry though due\nto the weird upper-casing and because it doesn't really tell you what it\neven intends to do.\n\nRename the job to \"linux-feature-testbed\" instead.\n\nHelped-by: Junio C Hamano <gitster@pobox.com>\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 2 +-\n .gitlab-ci.yml             | 2 +-\n ci/run-build-and-tests.sh  | 2 +-\n 3 files changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex 6d1e37c8f1..60f262db39 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -408,7 +408,7 @@ jobs:\n         - jobname: linux-reftable\n           image: ubuntu:rolling\n           cc: clang\n-        - jobname: linux-TEST-vars\n+        - jobname: linux-feature-testbed\n           image: ubuntu:20.04\n           cc: gcc\n           cc_package: gcc-8\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 7d972f0c8b..726c1c1865 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -42,7 +42,7 @@ test:linux:\n       - jobname: linux-reftable\n         image: ubuntu:rolling\n         CC: clang\n-      - jobname: linux-TEST-vars\n+      - jobname: linux-feature-testbed\n         image: ubuntu:20.04\n         CC: gcc\n         CC_PACKAGE: gcc-8\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex 23e87cbbd6..611bf6e56d 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -22,7 +22,7 @@ fedora-breaking-changes-meson|linux-breaking-changes)\n \texport WITH_BREAKING_CHANGES=YesPlease\n \tMESONFLAGS=\"$MESONFLAGS -Dbreaking_changes=true\"\n \t;;\n-linux-TEST-vars)\n+linux-feature-testbed)\n \texport OPENSSL_SHA1_UNSAFE=YesPlease\n \texport GIT_TEST_SPLIT_INDEX=yes\n \texport GIT_TEST_FULL_IN_PACK_ARRAY=true\n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"554970","messageId":"20261014-pks-ci-housekeeping-v3-6-04c24e1f480d@pks.im","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im","subject":"[PATCH v3 6/8] ci: switch away from EOL'd Ubuntu version in linux-feature-testbed","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T08:30:32Z","receivedAt":"2026-10-14T08:30:32Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"linux-feature-testbed\" job still uses Ubuntu 20.04, which is end of\nlife nowadays and starting to show some cracks. Switch it over to use\nthe \"latest\" tag instead so that we don't have to constantly update it\nanymore.\n\nNow arguably, this reduces test coverage for old versions of Ubuntu.\nBut \"latest\" at least points to the most up-to-date LTS release of\nUbuntu, compared to the \"rolling\" tag that uses the latest release\nregardless of the LTS status. So while \"latest\" and \"rolling\" are the\nsame right now, that's not always the case.\n\nFurthermore, we have other jobs that test with ancient versions of\nLinux, like for example the one that uses AlmaLinux 8 (2021, originally\ntracking RHEL 8 from 2019) or Debian 12 (2023).\n\nNote that this also requires us to switch away from GCC 8, which is not\nsupported by Ubuntu 26.04 anymore. Instead we simply use the default\nversion of GCC.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 4 +---\n .gitlab-ci.yml             | 4 +---\n 2 files changed, 2 insertions(+), 6 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex 60f262db39..47f174ed0e 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -409,9 +409,7 @@ jobs:\n           image: ubuntu:rolling\n           cc: clang\n         - jobname: linux-feature-testbed\n-          image: ubuntu:20.04\n-          cc: gcc\n-          cc_package: gcc-8\n+          image: ubuntu:latest\n         - jobname: linux-breaking-changes\n           cc: gcc\n           image: ubuntu:rolling\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 726c1c1865..3e2e6083cb 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -43,9 +43,7 @@ test:linux:\n         image: ubuntu:rolling\n         CC: clang\n       - jobname: linux-feature-testbed\n-        image: ubuntu:20.04\n-        CC: gcc\n-        CC_PACKAGE: gcc-8\n+        image: ubuntu:latest\n       - jobname: linux-breaking-changes\n         image: ubuntu:rolling\n         CC: gcc\n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"554971","messageId":"20261014-pks-ci-housekeeping-v3-7-04c24e1f480d@pks.im","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im","subject":"[PATCH v3 7/8] ci: drop now-dead Python 2 coverage","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T08:30:33Z","receivedAt":"2026-10-14T08:30:33Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"In the preceding commit we've dropped the last job that still used\nUbuntu 20.04. We still had some conditional logic for that specific\nimage that made us use Python 2 instead of Python 3, but this is dead\ncode now.\n\nWe could of course exercise Python 2 in any of our other CI jobs. But it\nreached end of life in 2020 already, and none of the distros that we use\nhave it packaged anymore. Furthermore, it seems like the world has\nfinally adapted to Python 3. So it doesn't feel all that useful to still\nexercise it.\n\nDrop the logic and instead use Python 3 unconditionally.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n ci/install-dependencies.sh |  2 +-\n ci/lib.sh                  | 11 +----------\n 2 files changed, 2 insertions(+), 11 deletions(-)\n\ndiff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh\nindex 8783b48951..4b1733ad15 100755\n--- a/ci/install-dependencies.sh\n+++ b/ci/install-dependencies.sh\n@@ -61,7 +61,7 @@ ubuntu-*|i386/debian-*|debian-*)\n \t\ttcl tk gettext zlib1g-dev perl-modules liberror-perl libauthen-sasl-perl \\\n \t\tlibemail-valid-perl libio-pty-perl libio-socket-ssl-perl libnet-smtp-ssl-perl libdbd-sqlite3-perl libcgi-pm-perl \\\n \t\tlibsecret-1-dev libpcre2-dev meson ninja-build pkg-config cargo \\\n-\t\t${CC_PACKAGE:-${CC:-gcc}} $PYTHON_PACKAGE\n+\t\t${CC_PACKAGE:-${CC:-gcc}} python3\n \n \t# Starting with Ubuntu 25.10, sudo can now be provided via either\n \t# sudo(1) or sudo-rs(1), with the latter being the default. The problem\ndiff --git a/ci/lib.sh b/ci/lib.sh\nindex d99e7b9da1..3ec10488d4 100755\n--- a/ci/lib.sh\n+++ b/ci/lib.sh\n@@ -335,16 +335,7 @@ esac\n \n case \"$distro\" in\n ubuntu-*)\n-\t# Python 2 is end of life, and Ubuntu 23.04 and newer don't actually\n-\t# have it anymore. We thus only test with Python 2 on older LTS\n-\t# releases.\n-\tif test \"$distro\" = \"ubuntu-20.04\"\n-\tthen\n-\t\tPYTHON_PACKAGE=python2\n-\telse\n-\t\tPYTHON_PACKAGE=python3\n-\tfi\n-\tMAKEFLAGS=\"$MAKEFLAGS PYTHON_PATH=/usr/bin/$PYTHON_PACKAGE\"\n+\tMAKEFLAGS=\"$MAKEFLAGS PYTHON_PATH=/usr/bin/python3\"\n \n \texport GIT_TEST_HTTPD=true\n \n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"554972","messageId":"20261014-pks-ci-housekeeping-v3-8-04c24e1f480d@pks.im","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im","subject":"[PATCH v3 8/8] ci: improve reftable test coverage","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T08:30:34Z","receivedAt":"2026-10-14T08:30:34Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"linux-reftable\" job exercises Git with reftables as its default\nbackend. But this job is arguably redundant because we already have the\n\"linux-reftable-leaks\" job that exercises reftables with the leak\nsanitizer enabled, and it is unlikely that we will catch any extra bugs\nwith the leak sanitizer disabled.\n\nOne may thus be triggered to just drop the \"linux-reftable\" job in favor\nof the leak-checking variant. But the latter disables a couple of other\ntests that exercise git-p4, git-svn and other tools. Those tools may not\nbe an essential part of Git nowadays, but I don't quite feel comfortable\nwith reducing test coverage.\n\nInstead, adapt the job to run reftables together with SHA256. which is\nan area that we don't have test coverage for.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 2 +-\n .gitlab-ci.yml             | 2 +-\n ci/run-build-and-tests.sh  | 6 +++++-\n 3 files changed, 7 insertions(+), 3 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex 47f174ed0e..fe8155772a 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -405,7 +405,7 @@ jobs:\n         - jobname: linux-sha256\n           image: ubuntu:rolling\n           cc: clang\n-        - jobname: linux-reftable\n+        - jobname: linux-reftable-sha256\n           image: ubuntu:rolling\n           cc: clang\n         - jobname: linux-feature-testbed\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 3e2e6083cb..9b7698a003 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -39,7 +39,7 @@ test:linux:\n       - jobname: linux-sha256\n         image: ubuntu:rolling\n         CC: clang\n-      - jobname: linux-reftable\n+      - jobname: linux-reftable-sha256\n         image: ubuntu:rolling\n         CC: clang\n       - jobname: linux-feature-testbed\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex 611bf6e56d..1c549634e0 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -40,7 +40,11 @@ linux-feature-testbed)\n linux-sha256)\n \texport GIT_TEST_DEFAULT_HASH=sha256\n \t;;\n-linux-reftable|linux-reftable-leaks|osx-reftable)\n+linux-reftable-sha256)\n+\texport GIT_TEST_DEFAULT_HASH=sha256\n+\texport GIT_TEST_DEFAULT_REF_STORAGE_FORMAT=reftable\n+\t;;\n+linux-reftable-leaks|osx-reftable)\n \texport GIT_TEST_DEFAULT_REF_STORAGE_FORMAT=reftable\n \t;;\n \n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"554981","messageId":"20261014090746.GA1341124@coredump.intra.peff.net","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-1-04c24e1f480d@pks.im","subject":"Re: [PATCH v3 1/8] t5004: skip SHA-1-only test in SHA-256 repository","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2026-10-14T09:07:46Z","receivedAt":"2026-10-14T09:07:46Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Oct 14, 2026 at 10:30:27AM +0200, Patrick Steinhardt wrote:\n\n> We're about to fix that typo in the next commit, but this will also\n> uncover that the above test case is broken when running in SHA-256\n> repositories. The extracted objects are SHA-1 objects, so extracting\n> them into a SHA-256 repository is not going to yield anything good. So\n> once we fix the Fedora-based job to enable breaking changes, which will\n> make tests use SHA-256 by default, the test will break.\n> \n> Fix this issue by adding the SHA1 prerequisite.\n\nDoes that mean we'll basically never run the test once Git 3.0 shifts to\nsha256 by default? I guess we'll have a sha1 ci job (like we have sha256\ntoday), but would that job actually hit all the other prereqs?\n\nIf we instead teach it to use its own repo, independent of the defaults,\nthen we could run it everywhere (that allows all of the other prereqs).\n\nSomething like:\n\ndiff --git a/t/t5004-archive-corner-cases.sh b/t/t5004-archive-corner-cases.sh\nindex 768b0ff85d..3a5c01c475 100755\n--- a/t/t5004-archive-corner-cases.sh\n+++ b/t/t5004-archive-corner-cases.sh\n@@ -187,6 +187,9 @@ test_expect_success EXPENSIVE,UNZIP,UNZIP_ZIP64_SUPPORT \\\n \n test_expect_success EXPENSIVE,LONG_IS_64BIT,UNZIP,UNZIP_ZIP64_SUPPORT,ZIPINFO \\\n \t'zip archive with files bigger than 4GB' '\n+\tgit init --object-format=sha1 big-file &&\n+\t(\n+\tcd big-file &&\n \t# Pack created with:\n \t#   dd if=/dev/zero of=file bs=1M count=4100 && git hash-object -w file\n \tmkdir -p .git/objects/pack &&\n@@ -206,6 +209,7 @@ test_expect_success EXPENSIVE,LONG_IS_64BIT,UNZIP,UNZIP_ZIP64_SUPPORT,ZIPINFO \\\n \t\"$GIT_UNZIP\" -t big.zip &&\n \t\"$ZIPINFO\" big.zip >big.lst &&\n \ttest_grep $size big.lst\n+\t)\n '\n \n build_tree() {\n\n\nA real patch obviously would also indent the test body one level; I\nskipped that here to keep the diff readable.\n\n-Peff\n\n"},{"id":"554982","messageId":"20261014091037.GB1341124@coredump.intra.peff.net","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-2-04c24e1f480d@pks.im","subject":"Re: [PATCH v3 2/8] ci: fix \"fedora-breaking-changes-meson\" job","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2026-10-14T09:10:37Z","receivedAt":"2026-10-14T09:10:37Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Oct 14, 2026 at 10:30:28AM +0200, Patrick Steinhardt wrote:\n\n> The \"fedora-breaking-changes-meson\" job exercises Git with breaking\n> changes enabled on Fedora with Meson. There's a typo in our CI scripts\n> though, which has the effect that the build does not enable breaking\n> changes by accident.\n>\n> [...]\n>\n>  case \"$jobname\" in\n> -fedora-breaking-changes-musl|linux-breaking-changes)\n> +fedora-breaking-changes-meson|linux-breaking-changes)\n>  \texport WITH_BREAKING_CHANGES=YesPlease\n>  \tMESONFLAGS=\"$MESONFLAGS -Dbreaking_changes=true\"\n>  \t;;\n\nSeems obviously correct, but I wonder if just:\n\n  *breaking-changes*)\n\nwould fix this and prevent any issues for possible future jobs. The\ndownside of a loose pattern is false matches, but it seems like a small\nrisk given our universe of jobs.\n\n-Peff\n\n"},{"id":"554983","messageId":"20261014091705.GC1341124@coredump.intra.peff.net","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-4-04c24e1f480d@pks.im","subject":"Re: [PATCH v3 4/8] ci: switch away from unsupported i386/ubuntu image","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2026-10-14T09:17:05Z","receivedAt":"2026-10-14T09:17:05Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Oct 14, 2026 at 10:30:30AM +0200, Patrick Steinhardt wrote:\n\n> The linux32 job is used to exercise Git on a 32 bit platform. That job\n> uses i386/ubuntu:20.04 though, and that version of Ubuntu is end of life\n> nowadays. Furthermore, Ubuntu 20.04 is the last release that has support\n> for 32 bit, so we cannot upgrade the image to a later version, either.\n> \n> Switch the job over to use i386/debian instead. Note that starting with\n> Debian 13, support for i386 has been reduced [1]. But Debian still\n> releases 32 bit Docker images for the latest release nowadays, so we\n> will have coverage until at least 2030.\n\nMakes sense. I did notice this hunk, though:\n\n> @@ -48,10 +48,6 @@ ubuntu-*|i386/ubuntu-*|debian-*)\n>  \t\tSVN='libsvn-perl subversion'\n>  \t\tLANGUAGES='language-pack-is'\n>  \t\t;;\n> -\ti386/ubuntu-*)\n> -\t\tSVN=\n> -\t\tLANGUAGES='language-pack-is'\n> -\t\t;;\n\nI think we have some tests which use is_IS as an exotic locale, which I\nassume is why we add this dependency. Do we need to do something similar\nfor Debian so we don't skip those gettext tests on the 32-bit job, or\ndoes it just work on Debian?\n\n-Peff\n\n"},{"id":"554984","messageId":"20261014091759.GD1341124@coredump.intra.peff.net","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-5-04c24e1f480d@pks.im","subject":"Re: [PATCH v3 5/8] ci: rename linux-TEST-vars job","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2026-10-14T09:17:59Z","receivedAt":"2026-10-14T09:17:59Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Oct 14, 2026 at 10:30:31AM +0200, Patrick Steinhardt wrote:\n\n> The \"linux-TEST-vars\" job exercises Git with a bunch of non-default\n> options enabled. The name of that job makes you want to cry though due\n> to the weird upper-casing and because it doesn't really tell you what it\n> even intends to do.\n\nFWIW, I have always hated the name, too. ;)\n\n> Rename the job to \"linux-feature-testbed\" instead.\n\nI saw the name discussion upthread, and I agree this one is good.\n\n-Peff\n\n"},{"id":"554985","messageId":"20261014091843.GE1341124@coredump.intra.peff.net","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-6-04c24e1f480d@pks.im","subject":"Re: [PATCH v3 6/8] ci: switch away from EOL'd Ubuntu version in linux-feature-testbed","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2026-10-14T09:18:43Z","receivedAt":"2026-10-14T09:18:43Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Oct 14, 2026 at 10:30:32AM +0200, Patrick Steinhardt wrote:\n\n> The \"linux-feature-testbed\" job still uses Ubuntu 20.04, which is end of\n> life nowadays and starting to show some cracks. Switch it over to use\n> the \"latest\" tag instead so that we don't have to constantly update it\n> anymore.\n> \n> Now arguably, this reduces test coverage for old versions of Ubuntu.\n> But \"latest\" at least points to the most up-to-date LTS release of\n> Ubuntu, compared to the \"rolling\" tag that uses the latest release\n> regardless of the LTS status. So while \"latest\" and \"rolling\" are the\n> same right now, that's not always the case.\n> \n> Furthermore, we have other jobs that test with ancient versions of\n> Linux, like for example the one that uses AlmaLinux 8 (2021, originally\n> tracking RHEL 8 from 2019) or Debian 12 (2023).\n\nYep, nicely explained and I agree this is a good direction.\n\n-Peff\n\n"},{"id":"554986","messageId":"20261014092137.GF1341124@coredump.intra.peff.net","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-8-04c24e1f480d@pks.im","subject":"Re: [PATCH v3 8/8] ci: improve reftable test coverage","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2026-10-14T09:21:37Z","receivedAt":"2026-10-14T09:21:37Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Oct 14, 2026 at 10:30:34AM +0200, Patrick Steinhardt wrote:\n\n> The \"linux-reftable\" job exercises Git with reftables as its default\n> backend. But this job is arguably redundant because we already have the\n> \"linux-reftable-leaks\" job that exercises reftables with the leak\n> sanitizer enabled, and it is unlikely that we will catch any extra bugs\n> with the leak sanitizer disabled.\n> \n> One may thus be triggered to just drop the \"linux-reftable\" job in favor\n> of the leak-checking variant. But the latter disables a couple of other\n> tests that exercise git-p4, git-svn and other tools. Those tools may not\n> be an essential part of Git nowadays, but I don't quite feel comfortable\n> with reducing test coverage.\n> \n> Instead, adapt the job to run reftables together with SHA256. which is\n> an area that we don't have test coverage for.\n\nHmm. Aren't both sha256 and reftables by default part of the breaking\nchanges flag? So I think we probably are already getting coverage there.\n\n-Peff\n\n"},{"id":"554987","messageId":"20261014092244.GG1341124@coredump.intra.peff.net","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im","subject":"Re: [PATCH v3 0/8] ci: some housekeeping and modernizations","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2026-10-14T09:22:44Z","receivedAt":"2026-10-14T09:22:44Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Oct 14, 2026 at 10:30:26AM +0200, Patrick Steinhardt wrote:\n\n> this patch series is a result from the discussions in [1]. It fixes a\n> couple of smaller issues in our CI and bumps jobs that use EOL Docker\n> images to instead use supported ones.\n> \n> Passing test runs can be found at [2] and [3] for GitLab and GitHub,\n> respectively.\n\nSorry I missed the earlier rounds. The overall direction looks good to\nme, and thanks for working on this. I did raise a few small issues that\nmight be worth addressing.\n\n-Peff\n\n"},{"id":"554995","messageId":"as9a0znMFrbOm5s1@pks.im","threadId":"66489","inReplyTo":"20261014090746.GA1341124@coredump.intra.peff.net","subject":"Re: [PATCH v3 1/8] t5004: skip SHA-1-only test in SHA-256 repository","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T10:34:59Z","receivedAt":"2026-10-14T10:34:59Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Wed, Oct 14, 2026 at 05:07:46AM -0400, Jeff King wrote:\n> On Wed, Oct 14, 2026 at 10:30:27AM +0200, Patrick Steinhardt wrote:\n> \n> > We're about to fix that typo in the next commit, but this will also\n> > uncover that the above test case is broken when running in SHA-256\n> > repositories. The extracted objects are SHA-1 objects, so extracting\n> > them into a SHA-256 repository is not going to yield anything good. So\n> > once we fix the Fedora-based job to enable breaking changes, which will\n> > make tests use SHA-256 by default, the test will break.\n> > \n> > Fix this issue by adding the SHA1 prerequisite.\n> \n> Does that mean we'll basically never run the test once Git 3.0 shifts to\n> sha256 by default? I guess we'll have a sha1 ci job (like we have sha256\n> today), but would that job actually hit all the other prereqs?\n> \n> If we instead teach it to use its own repo, independent of the defaults,\n> then we could run it everywhere (that allows all of the other prereqs).\n> \n> Something like:\n> \n> diff --git a/t/t5004-archive-corner-cases.sh b/t/t5004-archive-corner-cases.sh\n> index 768b0ff85d..3a5c01c475 100755\n> --- a/t/t5004-archive-corner-cases.sh\n> +++ b/t/t5004-archive-corner-cases.sh\n> @@ -187,6 +187,9 @@ test_expect_success EXPENSIVE,UNZIP,UNZIP_ZIP64_SUPPORT \\\n>  \n>  test_expect_success EXPENSIVE,LONG_IS_64BIT,UNZIP,UNZIP_ZIP64_SUPPORT,ZIPINFO \\\n>  \t'zip archive with files bigger than 4GB' '\n> +\tgit init --object-format=sha1 big-file &&\n> +\t(\n> +\tcd big-file &&\n>  \t# Pack created with:\n>  \t#   dd if=/dev/zero of=file bs=1M count=4100 && git hash-object -w file\n>  \tmkdir -p .git/objects/pack &&\n> @@ -206,6 +209,7 @@ test_expect_success EXPENSIVE,LONG_IS_64BIT,UNZIP,UNZIP_ZIP64_SUPPORT,ZIPINFO \\\n>  \t\"$GIT_UNZIP\" -t big.zip &&\n>  \t\"$ZIPINFO\" big.zip >big.lst &&\n>  \ttest_grep $size big.lst\n> +\t)\n>  '\n>  \n>  build_tree() {\n> \n> \n> A real patch obviously would also indent the test body one level; I\n> skipped that here to keep the diff readable.\n\nHmm. Yeah, I guess that wouldn't hurt.\n\nPatrick\n\n"},{"id":"554997","messageId":"as9a3E6NeR_sQeYd@pks.im","threadId":"66489","inReplyTo":"20261014091037.GB1341124@coredump.intra.peff.net","subject":"Re: [PATCH v3 2/8] ci: fix \"fedora-breaking-changes-meson\" job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T10:35:08Z","receivedAt":"2026-10-14T10:35:08Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Wed, Oct 14, 2026 at 05:10:37AM -0400, Jeff King wrote:\n> On Wed, Oct 14, 2026 at 10:30:28AM +0200, Patrick Steinhardt wrote:\n> \n> > The \"fedora-breaking-changes-meson\" job exercises Git with breaking\n> > changes enabled on Fedora with Meson. There's a typo in our CI scripts\n> > though, which has the effect that the build does not enable breaking\n> > changes by accident.\n> >\n> > [...]\n> >\n> >  case \"$jobname\" in\n> > -fedora-breaking-changes-musl|linux-breaking-changes)\n> > +fedora-breaking-changes-meson|linux-breaking-changes)\n> >  \texport WITH_BREAKING_CHANGES=YesPlease\n> >  \tMESONFLAGS=\"$MESONFLAGS -Dbreaking_changes=true\"\n> >  \t;;\n> \n> Seems obviously correct, but I wonder if just:\n> \n>   *breaking-changes*)\n> \n> would fix this and prevent any issues for possible future jobs. The\n> downside of a loose pattern is false matches, but it seems like a small\n> risk given our universe of jobs.\n\nIn general I think the way we structure these is somewhat lackluster:\n\n  - I never really understood the split between \"ci/lib.sh\" and\n    \"ci/run-build-and-tests.sh\".\n\n  - There is a bunch of duplication that could be avoided.\n\n  - And your suggestion makes sense, too.\n\nI originally carried a patch that merges all of this into \"ci/lib.sh\",\nand it also did changes similar to what you propose. We could probably\nrevive that patch, but if so I'd propose to do that as a follow-up.\n\nPatrick\n\n"},{"id":"554998","messageId":"as9a4WHSXY4pagpp@pks.im","threadId":"66489","inReplyTo":"20261014091705.GC1341124@coredump.intra.peff.net","subject":"Re: [PATCH v3 4/8] ci: switch away from unsupported i386/ubuntu image","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T10:35:13Z","receivedAt":"2026-10-14T10:35:13Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Wed, Oct 14, 2026 at 05:17:05AM -0400, Jeff King wrote:\n> On Wed, Oct 14, 2026 at 10:30:30AM +0200, Patrick Steinhardt wrote:\n> \n> > The linux32 job is used to exercise Git on a 32 bit platform. That job\n> > uses i386/ubuntu:20.04 though, and that version of Ubuntu is end of life\n> > nowadays. Furthermore, Ubuntu 20.04 is the last release that has support\n> > for 32 bit, so we cannot upgrade the image to a later version, either.\n> > \n> > Switch the job over to use i386/debian instead. Note that starting with\n> > Debian 13, support for i386 has been reduced [1]. But Debian still\n> > releases 32 bit Docker images for the latest release nowadays, so we\n> > will have coverage until at least 2030.\n> \n> Makes sense. I did notice this hunk, though:\n> \n> > @@ -48,10 +48,6 @@ ubuntu-*|i386/ubuntu-*|debian-*)\n> >  \t\tSVN='libsvn-perl subversion'\n> >  \t\tLANGUAGES='language-pack-is'\n> >  \t\t;;\n> > -\ti386/ubuntu-*)\n> > -\t\tSVN=\n> > -\t\tLANGUAGES='language-pack-is'\n> > -\t\t;;\n> \n> I think we have some tests which use is_IS as an exotic locale, which I\n> assume is why we add this dependency. Do we need to do something similar\n> for Debian so we don't skip those gettext tests on the 32-bit job, or\n> does it just work on Debian?\n\nOn Debian we already install \"locales-all\", so I don't think we have to\ndo anything there.\n\nPatrick\n\n"},{"id":"554999","messageId":"as9a5RngDLM8Miue@pks.im","threadId":"66489","inReplyTo":"20261014092137.GF1341124@coredump.intra.peff.net","subject":"Re: [PATCH v3 8/8] ci: improve reftable test coverage","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T10:35:17Z","receivedAt":"2026-10-14T10:35:17Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Wed, Oct 14, 2026 at 05:21:37AM -0400, Jeff King wrote:\n> On Wed, Oct 14, 2026 at 10:30:34AM +0200, Patrick Steinhardt wrote:\n> \n> > The \"linux-reftable\" job exercises Git with reftables as its default\n> > backend. But this job is arguably redundant because we already have the\n> > \"linux-reftable-leaks\" job that exercises reftables with the leak\n> > sanitizer enabled, and it is unlikely that we will catch any extra bugs\n> > with the leak sanitizer disabled.\n> > \n> > One may thus be triggered to just drop the \"linux-reftable\" job in favor\n> > of the leak-checking variant. But the latter disables a couple of other\n> > tests that exercise git-p4, git-svn and other tools. Those tools may not\n> > be an essential part of Git nowadays, but I don't quite feel comfortable\n> > with reducing test coverage.\n> > \n> > Instead, adapt the job to run reftables together with SHA256. which is\n> > an area that we don't have test coverage for.\n> \n> Hmm. Aren't both sha256 and reftables by default part of the breaking\n> changes flag? So I think we probably are already getting coverage there.\n\nSHA256 is, but reftables is not. Quoting \"t/test-lib.sh\":\n\n  GIT_TEST_BUILTIN_HASH=$(\"$GIT_BINARY\" version --build-options | sed -ne 's/^default-hash: //p')\n  GIT_DEFAULT_HASH=\"${GIT_TEST_DEFAULT_HASH:-$GIT_TEST_BUILTIN_HASH}\"\n  export GIT_DEFAULT_HASH\n  GIT_DEFAULT_REF_STORAGE_FORMAT=\"${GIT_TEST_DEFAULT_REF_STORAGE_FORMAT:-files}\"\n  export GIT_DEFAULT_REF_STORAGE_FORMAT\n\nSo we will run our tests with the default hash function, but we will\nrun with the \"files\" backend by default.\n\nPatrick\n\n"},{"id":"555005","messageId":"20261014110716.GC1356555@coredump.intra.peff.net","threadId":"66489","inReplyTo":"as9a3E6NeR_sQeYd@pks.im","subject":"Re: [PATCH v3 2/8] ci: fix \"fedora-breaking-changes-meson\" job","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2026-10-14T11:07:16Z","receivedAt":"2026-10-14T11:07:16Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Oct 14, 2026 at 12:35:08PM +0200, Patrick Steinhardt wrote:\n\n> > Seems obviously correct, but I wonder if just:\n> > \n> >   *breaking-changes*)\n> > \n> > would fix this and prevent any issues for possible future jobs. The\n> > downside of a loose pattern is false matches, but it seems like a small\n> > risk given our universe of jobs.\n> \n> In general I think the way we structure these is somewhat lackluster:\n> \n>   - I never really understood the split between \"ci/lib.sh\" and\n>     \"ci/run-build-and-tests.sh\".\n> \n>   - There is a bunch of duplication that could be avoided.\n> \n>   - And your suggestion makes sense, too.\n\nYeah, I think there is a combination of organic growth and the fact that\nnobody really cares about ci unless it's failing. It is probably ripe\nfor cleanup if somebody cares to spend time on it.\n\n> I originally carried a patch that merges all of this into \"ci/lib.sh\",\n> and it also did changes similar to what you propose. We could probably\n> revive that patch, but if so I'd propose to do that as a follow-up.\n\nI'm OK with doing it later. I noticed some other similar spots in the\ncontext while reading your patches. E.g., anything with *-sha256* could\nset the default hash, and so on. I expect you might have found them for\nyour patch, too. ;)\n\n-Peff\n\n"},{"id":"555006","messageId":"20261014110822.GD1356555@coredump.intra.peff.net","threadId":"66489","inReplyTo":"as9a4WHSXY4pagpp@pks.im","subject":"Re: [PATCH v3 4/8] ci: switch away from unsupported i386/ubuntu image","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2026-10-14T11:08:22Z","receivedAt":"2026-10-14T11:08:22Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Oct 14, 2026 at 12:35:13PM +0200, Patrick Steinhardt wrote:\n\n> > Makes sense. I did notice this hunk, though:\n> > \n> > > @@ -48,10 +48,6 @@ ubuntu-*|i386/ubuntu-*|debian-*)\n> > >  \t\tSVN='libsvn-perl subversion'\n> > >  \t\tLANGUAGES='language-pack-is'\n> > >  \t\t;;\n> > > -\ti386/ubuntu-*)\n> > > -\t\tSVN=\n> > > -\t\tLANGUAGES='language-pack-is'\n> > > -\t\t;;\n> > \n> > I think we have some tests which use is_IS as an exotic locale, which I\n> > assume is why we add this dependency. Do we need to do something similar\n> > for Debian so we don't skip those gettext tests on the 32-bit job, or\n> > does it just work on Debian?\n> \n> On Debian we already install \"locales-all\", so I don't think we have to\n> do anything there.\n\nThat makes sense. ISTR having to tell Debian which locales I cared\nabout, but I think that's because I _don't_ have locales-all installed.\n\n-Peff\n\n"},{"id":"555009","messageId":"20261014111344.GE1356555@coredump.intra.peff.net","threadId":"66489","inReplyTo":"as9a5RngDLM8Miue@pks.im","subject":"Re: [PATCH v3 8/8] ci: improve reftable test coverage","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2026-10-14T11:13:44Z","receivedAt":"2026-10-14T11:13:44Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Oct 14, 2026 at 12:35:17PM +0200, Patrick Steinhardt wrote:\n\n> > > Instead, adapt the job to run reftables together with SHA256. which is\n> > > an area that we don't have test coverage for.\n> > \n> > Hmm. Aren't both sha256 and reftables by default part of the breaking\n> > changes flag? So I think we probably are already getting coverage there.\n> \n> SHA256 is, but reftables is not. Quoting \"t/test-lib.sh\":\n> \n>   GIT_TEST_BUILTIN_HASH=$(\"$GIT_BINARY\" version --build-options | sed -ne 's/^default-hash: //p')\n>   GIT_DEFAULT_HASH=\"${GIT_TEST_DEFAULT_HASH:-$GIT_TEST_BUILTIN_HASH}\"\n>   export GIT_DEFAULT_HASH\n>   GIT_DEFAULT_REF_STORAGE_FORMAT=\"${GIT_TEST_DEFAULT_REF_STORAGE_FORMAT:-files}\"\n>   export GIT_DEFAULT_REF_STORAGE_FORMAT\n> \n> So we will run our tests with the default hash function, but we will\n> run with the \"files\" backend by default.\n\nAh, OK. That feels...weird, since the point of WITH_BREAKING_CHANGES is\nto check the new changes. Maybe reftables aren't breaking enough? :)\n\nI'd say we can punt it to another day, but if we _do_ think it's a bug,\nand we fix it, then that would make this new job pointless. I dunno.\nMaybe there is a good reason we are not pulling the ref format from\nbuild-options in the same way.\n\n"},{"id":"555010","messageId":"as9lGraxDWjEjhCK@pks.im","threadId":"66489","inReplyTo":"20261014111344.GE1356555@coredump.intra.peff.net","subject":"Re: [PATCH v3 8/8] ci: improve reftable test coverage","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T11:18:50Z","receivedAt":"2026-10-14T11:18:50Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Wed, Oct 14, 2026 at 07:13:44AM -0400, Jeff King wrote:\n> On Wed, Oct 14, 2026 at 12:35:17PM +0200, Patrick Steinhardt wrote:\n> \n> > > > Instead, adapt the job to run reftables together with SHA256. which is\n> > > > an area that we don't have test coverage for.\n> > > \n> > > Hmm. Aren't both sha256 and reftables by default part of the breaking\n> > > changes flag? So I think we probably are already getting coverage there.\n> > \n> > SHA256 is, but reftables is not. Quoting \"t/test-lib.sh\":\n> > \n> >   GIT_TEST_BUILTIN_HASH=$(\"$GIT_BINARY\" version --build-options | sed -ne 's/^default-hash: //p')\n> >   GIT_DEFAULT_HASH=\"${GIT_TEST_DEFAULT_HASH:-$GIT_TEST_BUILTIN_HASH}\"\n> >   export GIT_DEFAULT_HASH\n> >   GIT_DEFAULT_REF_STORAGE_FORMAT=\"${GIT_TEST_DEFAULT_REF_STORAGE_FORMAT:-files}\"\n> >   export GIT_DEFAULT_REF_STORAGE_FORMAT\n> > \n> > So we will run our tests with the default hash function, but we will\n> > run with the \"files\" backend by default.\n> \n> Ah, OK. That feels...weird, since the point of WITH_BREAKING_CHANGES is\n> to check the new changes. Maybe reftables aren't breaking enough? :)\n\nYeah, I agree it's weird.\n\n> I'd say we can punt it to another day, but if we _do_ think it's a bug,\n> and we fix it, then that would make this new job pointless. I dunno.\n> Maybe there is a good reason we are not pulling the ref format from\n> build-options in the same way.\n\nAs you mentioned in a preceding message, it's probably just that stuff\nhas grown organically. We added the job when reftables was not slated as\na breaking change, so we couldn't really pull it from the build-options\nat that point in time.\n\nI'd punt on this for now and just leave this as-is, because right now it\nincreases our test coverage. But if we revisit I agree we should figure\nout whether this job is still worth it.\n\nPatrick\n\n"},{"id":"555011","messageId":"as9lIJK2YzbWOOE8@pks.im","threadId":"66489","inReplyTo":"20261014110716.GC1356555@coredump.intra.peff.net","subject":"Re: [PATCH v3 2/8] ci: fix \"fedora-breaking-changes-meson\" job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-14T11:18:56Z","receivedAt":"2026-10-14T11:18:56Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Wed, Oct 14, 2026 at 07:07:16AM -0400, Jeff King wrote:\n> On Wed, Oct 14, 2026 at 12:35:08PM +0200, Patrick Steinhardt wrote:\n> \n> > > Seems obviously correct, but I wonder if just:\n> > > \n> > >   *breaking-changes*)\n> > > \n> > > would fix this and prevent any issues for possible future jobs. The\n> > > downside of a loose pattern is false matches, but it seems like a small\n> > > risk given our universe of jobs.\n> > \n> > In general I think the way we structure these is somewhat lackluster:\n> > \n> >   - I never really understood the split between \"ci/lib.sh\" and\n> >     \"ci/run-build-and-tests.sh\".\n> > \n> >   - There is a bunch of duplication that could be avoided.\n> > \n> >   - And your suggestion makes sense, too.\n> \n> Yeah, I think there is a combination of organic growth and the fact that\n> nobody really cares about ci unless it's failing. It is probably ripe\n> for cleanup if somebody cares to spend time on it.\n> \n> > I originally carried a patch that merges all of this into \"ci/lib.sh\",\n> > and it also did changes similar to what you propose. We could probably\n> > revive that patch, but if so I'd propose to do that as a follow-up.\n> \n> I'm OK with doing it later. I noticed some other similar spots in the\n> context while reading your patches. E.g., anything with *-sha256* could\n> set the default hash, and so on. I expect you might have found them for\n> your patch, too. ;)\n\nYes. sha256, breaking-changes, reftables, meson all fall in the same\ncategory.\n\nPatrick\n\n"},{"id":"555024","messageId":"20261014134739.GB1935857@coredump.intra.peff.net","threadId":"66489","inReplyTo":"as9lGraxDWjEjhCK@pks.im","subject":"Re: [PATCH v3 8/8] ci: improve reftable test coverage","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2026-10-14T13:47:39Z","receivedAt":"2026-10-14T13:47:39Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Oct 14, 2026 at 01:18:50PM +0200, Patrick Steinhardt wrote:\n\n> > I'd say we can punt it to another day, but if we _do_ think it's a bug,\n> > and we fix it, then that would make this new job pointless. I dunno.\n> > Maybe there is a good reason we are not pulling the ref format from\n> > build-options in the same way.\n> \n> As you mentioned in a preceding message, it's probably just that stuff\n> has grown organically. We added the job when reftables was not slated as\n> a breaking change, so we couldn't really pull it from the build-options\n> at that point in time.\n> \n> I'd punt on this for now and just leave this as-is, because right now it\n> increases our test coverage. But if we revisit I agree we should figure\n> out whether this job is still worth it.\n\nThat's fine by me. We should just try to remember to re-evaluate the\nsha256-reftables job when that happens.\n\n-Peff\n\n"},{"id":"555026","messageId":"xmqqwlrktkzz.fsf@gitster.g","threadId":"66489","inReplyTo":"20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im","subject":"Re: [PATCH v3 0/8] ci: some housekeeping and modernizations","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-14T14:28:00Z","receivedAt":"2026-10-14T14:28:00Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n> Changes in v2:\n\nThis one is v3.\n\n>   - Improve commit messages.\n\nOK.\n\n>   - Rework the \"linux-reftable\" job to be more useful instead of\n>     dropping it.\n\nHappend in v2, IIRC.\n\n>   - Rename \"linux-exotic\" to \"linux-feature-testbed\".\n\nThis did happen in this v3 iteration.\n\nThis was built on the current master, but I backported to make it\napply directly on top of v2.56.0 so we could use ot when we need to\nupdate 'maint' and run CI on it later.\n\nThanks.\n\n"},{"id":"555031","messageId":"3888af48-339f-4b6a-ae84-88d0ad9caf07@gmail.com","threadId":"66489","inReplyTo":"as9a0znMFrbOm5s1@pks.im","subject":"Re: [PATCH v3 1/8] t5004: skip SHA-1-only test in SHA-256 repository","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2026-10-14T15:04:09Z","receivedAt":"2026-10-14T15:04:09Z","isPatch":true,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 10/14/26 16:04, Patrick Steinhardt wrote:\n> On Wed, Oct 14, 2026 at 05:07:46AM -0400, Jeff King wrote:\n>> On Wed, Oct 14, 2026 at 10:30:27AM +0200, Patrick Steinhardt wrote:\n>>\n>>> We're about to fix that typo in the next commit, but this will also\n>>> uncover that the above test case is broken when running in SHA-256\n>>> repositories. The extracted objects are SHA-1 objects, so extracting\n>>> them into a SHA-256 repository is not going to yield anything good. So\n>>> once we fix the Fedora-based job to enable breaking changes, which will\n>>> make tests use SHA-256 by default, the test will break.\n>>>\n>>> Fix this issue by adding the SHA1 prerequisite.\n>>\n>> Does that mean we'll basically never run the test once Git 3.0 shifts to\n>> sha256 by default? I guess we'll have a sha1 ci job (like we have sha256\n>> today), but would that job actually hit all the other prereqs?\n>>\n>> If we instead teach it to use its own repo, independent of the defaults,\n>> then we could run it everywhere (that allows all of the other prereqs).\n>>\n\nThat indeed sounds like a good idea.\n\nI 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.\n\nI 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.\n\n[1]: https://github.com/git/git/actions/runs/38526140649?pr=2445\n\n-- \nSivaraam\n\n\n"},{"id":"555096","messageId":"atBoE11OSvlFIKis@pks.im","threadId":"66489","inReplyTo":"xmqqwlrktkzz.fsf@gitster.g","subject":"Re: [PATCH v3 0/8] ci: some housekeeping and modernizations","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-15T05:43:47Z","receivedAt":"2026-10-15T05:43:47Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Wed, Oct 14, 2026 at 07:28:00AM -0700, Junio C Hamano wrote:\n> Patrick Steinhardt <ps@pks.im> writes:\n> \n> > Changes in v2:\n> \n> This one is v3.\n\nOops, no idea what happened here. The state I'm in right now with b4 is\nsomewhat broken. v2 and v3 are almost the same \n\n> >   - Improve commit messages.\n> \n> OK.\n> \n> >   - Rework the \"linux-reftable\" job to be more useful instead of\n> >     dropping it.\n> \n> Happend in v2, IIRC.\n> \n> >   - Rename \"linux-exotic\" to \"linux-feature-testbed\".\n> \n> This did happen in this v3 iteration.\n> \n> This was built on the current master, but I backported to make it\n> apply directly on top of v2.56.0 so we could use ot when we need to\n> update 'maint' and run CI on it later.\n\nMakes sense. I'll keep the base as-is for now. I assume it's less work\nfor you this way with a primed rerere cache.\n\nPatrick\n\n"},{"id":"555097","messageId":"atBoGE_R_EJhkEs0@pks.im","threadId":"66489","inReplyTo":"3888af48-339f-4b6a-ae84-88d0ad9caf07@gmail.com","subject":"Re: [PATCH v3 1/8] t5004: skip SHA-1-only test in SHA-256 repository","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-15T05:43:52Z","receivedAt":"2026-10-15T05:43:52Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Wed, Oct 14, 2026 at 08:34:09PM +0530, Kaartic Sivaraam wrote:\n> On 10/14/26 16:04, Patrick Steinhardt wrote:\n> > On Wed, Oct 14, 2026 at 05:07:46AM -0400, Jeff King wrote:\n> > > On Wed, Oct 14, 2026 at 10:30:27AM +0200, Patrick Steinhardt wrote:\n> > > \n> > > > We're about to fix that typo in the next commit, but this will also\n> > > > uncover that the above test case is broken when running in SHA-256\n> > > > repositories. The extracted objects are SHA-1 objects, so extracting\n> > > > them into a SHA-256 repository is not going to yield anything good. So\n> > > > once we fix the Fedora-based job to enable breaking changes, which will\n> > > > make tests use SHA-256 by default, the test will break.\n> > > > \n> > > > Fix this issue by adding the SHA1 prerequisite.\n> > > \n> > > Does that mean we'll basically never run the test once Git 3.0 shifts to\n> > > sha256 by default? I guess we'll have a sha1 ci job (like we have sha256\n> > > today), but would that job actually hit all the other prereqs?\n> > > \n> > > If we instead teach it to use its own repo, independent of the defaults,\n> > > then we could run it everywhere (that allows all of the other prereqs).\n> > > \n> \n> That indeed sounds like a good idea.\n> \n> I also wonder, though. How many CI jobs actually satisfy the prerequisite\n> after the change? From a quick look and guessing via the time it took the\n> t5004 jobs to run[1] it seems only the macOS jobs and on AlmaLinux 8 jobs\n> run the test. The linux jobs don't seem to run it. I suppose this is\n> expected behaviour.\n> \n> I wonder if it is worth mentioning in the commit message or not. FWIW, the\n> \"not a lot of jobs even exercise this.\" in the commit message made me want\n> to confirm if this job runs at all after the change.\n> \n> [1]: https://github.com/git/git/actions/runs/38526140649?pr=2445\n\nI guess it's less interesting which exact jobs run this, so I think I'll\nkeep this information out of the commit message for now.\n\nPatrick\n\n"},{"id":"555105","messageId":"20261015-pks-ci-housekeeping-v4-0-c2c88f1b198e@pks.im","threadId":"66489","inReplyTo":"20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im","subject":"[PATCH v4 0/8] ci: some housekeeping and modernizations","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-15T06:57:09Z","receivedAt":"2026-10-15T06:57:09Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"Hi,\n\nthis patch series is a result from the discussions in [1]. It fixes a\ncouple of smaller issues in our CI and bumps jobs that use EOL Docker\nimages to instead use supported ones.\n\nPassing test runs can be found at [2] and [3] for GitLab and GitHub,\nrespectively.\n\nNote that I've also merged the Meson changes (ps/meson-improvements at\nce4a600322 (gitlab-ci: fix hanging MSVC jobs, 2026-09-24)) in there so\nthat GitLab passes, but those are not strictly required as a dependency.\n\nChanges in v4:\n  - Make the test in t5004 work both with SHA1 and SHA256 by forcing the\n    repo to SHA1.\n  - Link to v3: https://patch.msgid.link/20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im\n\nChanges in v3:\n  - Rename \"linux-exotic\" to \"linux-feature-testbed\".\n  - Link to v2: https://lore.kernel.org/all/20261009-pks-ci-housekeeping-v2-0-6863d58ef691@pks.im\n\nChanges in v2:\n  - Improve commit messages.\n  - Rework the \"linux-reftable\" job to be more useful instead of\n    dropping it.\n  - Link to v1: https://patch.msgid.link/20261008-pks-ci-housekeeping-v1-0-baf015c589c0@pks.im\n\nThanks!\n\nPatrick\n\n[1]: <20260906151137.GA328152@coredump.intra.peff.net>\n[2]: https://gitlab.com/gitlab-org/git/-/merge_requests/687\n[3]: https://github.com/git/git/pull/2445\n\n---\nPatrick Steinhardt (8):\n      t5004: fix test creating an archive with large objects under SHA256\n      ci: fix \"fedora-breaking-changes-meson\" job\n      ci: drop unused \"linux-clang\" logic\n      ci: switch away from unsupported i386/ubuntu image\n      ci: rename linux-TEST-vars job\n      ci: switch away from EOL'd Ubuntu version in linux-feature-testbed\n      ci: drop now-dead Python 2 coverage\n      ci: improve reftable test coverage\n\n .github/workflows/main.yml      | 11 ++++-------\n .gitlab-ci.yml                  | 11 ++++-------\n ci/install-dependencies.sh      |  8 ++------\n ci/lib.sh                       | 13 ++-----------\n ci/run-build-and-tests.sh       | 14 +++++++-------\n t/t5004-archive-corner-cases.sh | 42 +++++++++++++++++++++++------------------\n 6 files changed, 43 insertions(+), 56 deletions(-)\n\nRange-diff versus v3:\n\n1:  507e7089ef < -:  ---------- t5004: skip SHA-1-only test in SHA-256 repository\n-:  ---------- > 1:  25e4fe2c09 t5004: fix test creating an archive with large objects under SHA256\n2:  f84df9f38b = 2:  10addd4745 ci: fix \"fedora-breaking-changes-meson\" job\n3:  1b881f2e9e = 3:  7e6ae01f41 ci: drop unused \"linux-clang\" logic\n4:  02a6626c5e = 4:  8a5707e477 ci: switch away from unsupported i386/ubuntu image\n5:  f515ac9160 = 5:  68d62caa4a ci: rename linux-TEST-vars job\n6:  5528b7d564 = 6:  d1bc4ddd69 ci: switch away from EOL'd Ubuntu version in linux-feature-testbed\n7:  a12f3fbef0 = 7:  5d52020434 ci: drop now-dead Python 2 coverage\n8:  5c37cb46f3 = 8:  c6b6e4c63a ci: improve reftable test coverage\n\n---\nbase-commit: 8e383dedc6bbc4fd7bbb203512fbf2eafc151e04\nchange-id: 20261008-pks-ci-housekeeping-4cf7fac3b0df\n\n\n"},{"id":"555106","messageId":"20261015-pks-ci-housekeeping-v4-1-c2c88f1b198e@pks.im","threadId":"66489","inReplyTo":"20261015-pks-ci-housekeeping-v4-0-c2c88f1b198e@pks.im","subject":"[PATCH v4 1/8] t5004: fix test creating an archive with large objects under SHA256","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-15T06:57:10Z","receivedAt":"2026-10-15T06:57:10Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"One of the tests in t5004 extracts a ZIP file that contains some objects\nlarger than 4GB and then double-checks whether we can read and archive\nsuch an object. That test has a bunch of prerequities: it requires a 64\nbit `long`, unzip with 64-bit support and it only runs when EXPENSIVE is\nenabled. Consequently, not a lot of jobs even exercise this.\n\nOne of the jobs that does run it though is our Fedora-based job, as it\nticks all the necessary boxes. But that job was silently broken: while\nthe intent was to run on Fedora with breaking changes enabled, they are\nin fact disabled due to a typo.\n\nWe're about to fix that typo in the next commit, but this will also\nuncover that the above test case is broken when running in SHA-256\nrepositories. The extracted objects are SHA-1 objects, so extracting\nthem into a SHA-256 repository is not going to yield anything good. So\nonce we fix the Fedora-based job to enable breaking changes, which will\nmake tests use SHA-256 by default, the test will break.\n\nFix this issue by explicitly creating the repository with the SHA1\nobject format.\n\nSuggested-by: Jeff King <peff@peff.net>\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n t/t5004-archive-corner-cases.sh | 42 +++++++++++++++++++++++------------------\n 1 file changed, 24 insertions(+), 18 deletions(-)\n\ndiff --git a/t/t5004-archive-corner-cases.sh b/t/t5004-archive-corner-cases.sh\nindex 768b0ff85d..13edfbe5bc 100755\n--- a/t/t5004-archive-corner-cases.sh\n+++ b/t/t5004-archive-corner-cases.sh\n@@ -187,25 +187,31 @@ test_expect_success EXPENSIVE,UNZIP,UNZIP_ZIP64_SUPPORT \\\n \n test_expect_success EXPENSIVE,LONG_IS_64BIT,UNZIP,UNZIP_ZIP64_SUPPORT,ZIPINFO \\\n \t'zip archive with files bigger than 4GB' '\n-\t# Pack created with:\n-\t#   dd if=/dev/zero of=file bs=1M count=4100 && git hash-object -w file\n-\tmkdir -p .git/objects/pack &&\n+\ttest_when_finished rm -rf big-file &&\n+\tgit init --object-format=sha1 big-file &&\n \t(\n-\t\tcd .git/objects/pack &&\n-\t\t\"$GIT_UNZIP\" \"$TEST_DIRECTORY\"/t5004/big-pack.zip\n-\t) &&\n-\tblob=754a93d6fada4c6873360e6cb4b209132271ab0e &&\n-\tsize=$(expr 4100 \"*\" 1024 \"*\" 1024) &&\n-\n-\t# create a tree containing the file\n-\ttree=$(echo \"100644 blob $blob\tbig-file\" | git mktree) &&\n-\n-\t# zip it, creating an archive with a file bigger than 4GB\n-\tgit archive -o big.zip $tree &&\n-\n-\t\"$GIT_UNZIP\" -t big.zip &&\n-\t\"$ZIPINFO\" big.zip >big.lst &&\n-\ttest_grep $size big.lst\n+\t\tcd big-file &&\n+\n+\t\t# Pack created with:\n+\t\t#   dd if=/dev/zero of=file bs=1M count=4100 && git hash-object -w file\n+\t\tmkdir -p .git/objects/pack &&\n+\t\t(\n+\t\t\tcd .git/objects/pack &&\n+\t\t\t\"$GIT_UNZIP\" \"$TEST_DIRECTORY\"/t5004/big-pack.zip\n+\t\t) &&\n+\t\tblob=754a93d6fada4c6873360e6cb4b209132271ab0e &&\n+\t\tsize=$(expr 4100 \"*\" 1024 \"*\" 1024) &&\n+\n+\t\t# create a tree containing the file\n+\t\ttree=$(echo \"100644 blob $blob\tbig-file\" | git mktree) &&\n+\n+\t\t# zip it, creating an archive with a file bigger than 4GB\n+\t\tgit archive -o big.zip $tree &&\n+\n+\t\t\"$GIT_UNZIP\" -t big.zip &&\n+\t\t\"$ZIPINFO\" big.zip >big.lst &&\n+\t\ttest_grep $size big.lst\n+\t)\n '\n \n build_tree() {\n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"555107","messageId":"20261015-pks-ci-housekeeping-v4-2-c2c88f1b198e@pks.im","threadId":"66489","inReplyTo":"20261015-pks-ci-housekeeping-v4-0-c2c88f1b198e@pks.im","subject":"[PATCH v4 2/8] ci: fix \"fedora-breaking-changes-meson\" job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-15T06:57:11Z","receivedAt":"2026-10-15T06:57:11Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"fedora-breaking-changes-meson\" job exercises Git with breaking\nchanges enabled on Fedora with Meson. There's a typo in our CI scripts\nthough, which has the effect that the build does not enable breaking\nchanges by accident.\n\nFix the typo.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n ci/run-build-and-tests.sh | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex 6a3b43b366..bc5058c917 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -18,7 +18,7 @@ almalinux-*|debian-*|fedora-*|linux-*)\n esac\n \n case \"$jobname\" in\n-fedora-breaking-changes-musl|linux-breaking-changes)\n+fedora-breaking-changes-meson|linux-breaking-changes)\n \texport WITH_BREAKING_CHANGES=YesPlease\n \tMESONFLAGS=\"$MESONFLAGS -Dbreaking_changes=true\"\n \t;;\n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"555108","messageId":"20261015-pks-ci-housekeeping-v4-3-c2c88f1b198e@pks.im","threadId":"66489","inReplyTo":"20261015-pks-ci-housekeeping-v4-0-c2c88f1b198e@pks.im","subject":"[PATCH v4 3/8] ci: drop unused \"linux-clang\" logic","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-15T06:57:12Z","receivedAt":"2026-10-15T06:57:12Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"In d88d727143 (ci: drop linux-clang job, 2023-06-01) we have dropped the\n\"linux-clang\" job because another job already uses Clang anyway. But we\nforgot to also drop the logic in \"ci/run-build-and-tests.sh\", so we now\nhave some unused logic in there.\n\nDrop it.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n ci/run-build-and-tests.sh | 4 ----\n 1 file changed, 4 deletions(-)\n\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex bc5058c917..23e87cbbd6 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -37,10 +37,6 @@ linux-TEST-vars)\n \texport GIT_TEST_CHECKOUT_WORKERS=2\n \texport GIT_TEST_PACK_USE_BITMAP_BOUNDARY_TRAVERSAL=1\n \t;;\n-linux-clang)\n-\texport NO_RUST=UnfortunatelyYes\n-\texport GIT_TEST_DEFAULT_HASH=sha1\n-\t;;\n linux-sha256)\n \texport GIT_TEST_DEFAULT_HASH=sha256\n \t;;\n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"555109","messageId":"20261015-pks-ci-housekeeping-v4-4-c2c88f1b198e@pks.im","threadId":"66489","inReplyTo":"20261015-pks-ci-housekeeping-v4-0-c2c88f1b198e@pks.im","subject":"[PATCH v4 4/8] ci: switch away from unsupported i386/ubuntu image","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-15T06:57:13Z","receivedAt":"2026-10-15T06:57:13Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The linux32 job is used to exercise Git on a 32 bit platform. That job\nuses i386/ubuntu:20.04 though, and that version of Ubuntu is end of life\nnowadays. Furthermore, Ubuntu 20.04 is the last release that has support\nfor 32 bit, so we cannot upgrade the image to a later version, either.\n\nSwitch the job over to use i386/debian instead. Note that starting with\nDebian 13, support for i386 has been reduced [1]. But Debian still\nreleases 32 bit Docker images for the latest release nowadays, so we\nwill have coverage until at least 2030.\n\n[1]: https://www.debian.org/releases/trixie/release-notes/issues.en.html#i386-reduced-support\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 3 +--\n .gitlab-ci.yml             | 3 +--\n ci/install-dependencies.sh | 6 +-----\n ci/lib.sh                  | 2 +-\n 4 files changed, 4 insertions(+), 10 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex b229739be8..6d1e37c8f1 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -431,9 +431,8 @@ jobs:\n           cc: gcc\n         - jobname: linux-musl-meson\n           image: alpine:latest\n-        # Supported until 2025-04-02.\n         - jobname: linux32\n-          image: i386/ubuntu:20.04\n+          image: i386/debian:latest\n         # A RHEL 8 compatible distro.  Supported until 2029-05-31.\n         - jobname: almalinux-8\n           image: almalinux:8\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 3f24835500..7d972f0c8b 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -65,9 +65,8 @@ test:linux:\n         CC: gcc\n       - jobname: linux-musl-meson\n         image: alpine:latest\n-        # Supported until 2025-04-02.\n       - jobname: linux32\n-        image: i386/ubuntu:20.04\n+        image: i386/debian:latest\n       # A RHEL 8 compatible distro.  Supported until 2029-05-31.\n       - jobname: almalinux-8\n         image: almalinux:8\ndiff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh\nindex d57dce5663..8783b48951 100755\n--- a/ci/install-dependencies.sh\n+++ b/ci/install-dependencies.sh\n@@ -39,7 +39,7 @@ fedora-*|almalinux-*)\n \tdnf -yq update >/dev/null &&\n \tdnf -yq install shadow-utils sudo make pkg-config gcc findutils diffutils perl python3 gawk gettext zlib-devel expat-devel openssl-devel curl-devel pcre2-devel $MESON_DEPS cargo >/dev/null\n \t;;\n-ubuntu-*|i386/ubuntu-*|debian-*)\n+ubuntu-*|i386/debian-*|debian-*)\n \t# Required so that apt doesn't wait for user input on certain packages.\n \texport DEBIAN_FRONTEND=noninteractive\n \n@@ -48,10 +48,6 @@ ubuntu-*|i386/ubuntu-*|debian-*)\n \t\tSVN='libsvn-perl subversion'\n \t\tLANGUAGES='language-pack-is'\n \t\t;;\n-\ti386/ubuntu-*)\n-\t\tSVN=\n-\t\tLANGUAGES='language-pack-is'\n-\t\t;;\n \t*)\n \t\tSVN='libsvn-perl subversion'\n \t\tLANGUAGES='locales-all'\ndiff --git a/ci/lib.sh b/ci/lib.sh\nindex c6ccbf8c17..d99e7b9da1 100755\n--- a/ci/lib.sh\n+++ b/ci/lib.sh\n@@ -262,7 +262,7 @@ then\n \t\tCI_OS_NAME=osx\n \t\tJOBS=$(nproc)\n \t\t;;\n-\t*,almalinux:*|*,alpine:*|*,debian:*|*,fedora:*|*,ubuntu:*|*,i386/ubuntu:*)\n+\t*,almalinux:*|*,alpine:*|*,debian:*|*,fedora:*|*,ubuntu:*|*,i386/debian:*)\n \t\tCI_OS_NAME=linux\n \t\tJOBS=$(nproc)\n \t\t;;\n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"555110","messageId":"20261015-pks-ci-housekeeping-v4-5-c2c88f1b198e@pks.im","threadId":"66489","inReplyTo":"20261015-pks-ci-housekeeping-v4-0-c2c88f1b198e@pks.im","subject":"[PATCH v4 5/8] ci: rename linux-TEST-vars job","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-15T06:57:14Z","receivedAt":"2026-10-15T06:57:14Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"linux-TEST-vars\" job exercises Git with a bunch of non-default\noptions enabled. The name of that job makes you want to cry though due\nto the weird upper-casing and because it doesn't really tell you what it\neven intends to do.\n\nRename the job to \"linux-feature-testbed\" instead.\n\nHelped-by: Junio C Hamano <gitster@pobox.com>\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 2 +-\n .gitlab-ci.yml             | 2 +-\n ci/run-build-and-tests.sh  | 2 +-\n 3 files changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex 6d1e37c8f1..60f262db39 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -408,7 +408,7 @@ jobs:\n         - jobname: linux-reftable\n           image: ubuntu:rolling\n           cc: clang\n-        - jobname: linux-TEST-vars\n+        - jobname: linux-feature-testbed\n           image: ubuntu:20.04\n           cc: gcc\n           cc_package: gcc-8\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 7d972f0c8b..726c1c1865 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -42,7 +42,7 @@ test:linux:\n       - jobname: linux-reftable\n         image: ubuntu:rolling\n         CC: clang\n-      - jobname: linux-TEST-vars\n+      - jobname: linux-feature-testbed\n         image: ubuntu:20.04\n         CC: gcc\n         CC_PACKAGE: gcc-8\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex 23e87cbbd6..611bf6e56d 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -22,7 +22,7 @@ fedora-breaking-changes-meson|linux-breaking-changes)\n \texport WITH_BREAKING_CHANGES=YesPlease\n \tMESONFLAGS=\"$MESONFLAGS -Dbreaking_changes=true\"\n \t;;\n-linux-TEST-vars)\n+linux-feature-testbed)\n \texport OPENSSL_SHA1_UNSAFE=YesPlease\n \texport GIT_TEST_SPLIT_INDEX=yes\n \texport GIT_TEST_FULL_IN_PACK_ARRAY=true\n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"555111","messageId":"20261015-pks-ci-housekeeping-v4-6-c2c88f1b198e@pks.im","threadId":"66489","inReplyTo":"20261015-pks-ci-housekeeping-v4-0-c2c88f1b198e@pks.im","subject":"[PATCH v4 6/8] ci: switch away from EOL'd Ubuntu version in linux-feature-testbed","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-15T06:57:15Z","receivedAt":"2026-10-15T06:57:15Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"linux-feature-testbed\" job still uses Ubuntu 20.04, which is end of\nlife nowadays and starting to show some cracks. Switch it over to use\nthe \"latest\" tag instead so that we don't have to constantly update it\nanymore.\n\nNow arguably, this reduces test coverage for old versions of Ubuntu.\nBut \"latest\" at least points to the most up-to-date LTS release of\nUbuntu, compared to the \"rolling\" tag that uses the latest release\nregardless of the LTS status. So while \"latest\" and \"rolling\" are the\nsame right now, that's not always the case.\n\nFurthermore, we have other jobs that test with ancient versions of\nLinux, like for example the one that uses AlmaLinux 8 (2021, originally\ntracking RHEL 8 from 2019) or Debian 12 (2023).\n\nNote that this also requires us to switch away from GCC 8, which is not\nsupported by Ubuntu 26.04 anymore. Instead we simply use the default\nversion of GCC.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 4 +---\n .gitlab-ci.yml             | 4 +---\n 2 files changed, 2 insertions(+), 6 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex 60f262db39..47f174ed0e 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -409,9 +409,7 @@ jobs:\n           image: ubuntu:rolling\n           cc: clang\n         - jobname: linux-feature-testbed\n-          image: ubuntu:20.04\n-          cc: gcc\n-          cc_package: gcc-8\n+          image: ubuntu:latest\n         - jobname: linux-breaking-changes\n           cc: gcc\n           image: ubuntu:rolling\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 726c1c1865..3e2e6083cb 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -43,9 +43,7 @@ test:linux:\n         image: ubuntu:rolling\n         CC: clang\n       - jobname: linux-feature-testbed\n-        image: ubuntu:20.04\n-        CC: gcc\n-        CC_PACKAGE: gcc-8\n+        image: ubuntu:latest\n       - jobname: linux-breaking-changes\n         image: ubuntu:rolling\n         CC: gcc\n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"555112","messageId":"20261015-pks-ci-housekeeping-v4-7-c2c88f1b198e@pks.im","threadId":"66489","inReplyTo":"20261015-pks-ci-housekeeping-v4-0-c2c88f1b198e@pks.im","subject":"[PATCH v4 7/8] ci: drop now-dead Python 2 coverage","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-15T06:57:16Z","receivedAt":"2026-10-15T06:57:16Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"In the preceding commit we've dropped the last job that still used\nUbuntu 20.04. We still had some conditional logic for that specific\nimage that made us use Python 2 instead of Python 3, but this is dead\ncode now.\n\nWe could of course exercise Python 2 in any of our other CI jobs. But it\nreached end of life in 2020 already, and none of the distros that we use\nhave it packaged anymore. Furthermore, it seems like the world has\nfinally adapted to Python 3. So it doesn't feel all that useful to still\nexercise it.\n\nDrop the logic and instead use Python 3 unconditionally.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n ci/install-dependencies.sh |  2 +-\n ci/lib.sh                  | 11 +----------\n 2 files changed, 2 insertions(+), 11 deletions(-)\n\ndiff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh\nindex 8783b48951..4b1733ad15 100755\n--- a/ci/install-dependencies.sh\n+++ b/ci/install-dependencies.sh\n@@ -61,7 +61,7 @@ ubuntu-*|i386/debian-*|debian-*)\n \t\ttcl tk gettext zlib1g-dev perl-modules liberror-perl libauthen-sasl-perl \\\n \t\tlibemail-valid-perl libio-pty-perl libio-socket-ssl-perl libnet-smtp-ssl-perl libdbd-sqlite3-perl libcgi-pm-perl \\\n \t\tlibsecret-1-dev libpcre2-dev meson ninja-build pkg-config cargo \\\n-\t\t${CC_PACKAGE:-${CC:-gcc}} $PYTHON_PACKAGE\n+\t\t${CC_PACKAGE:-${CC:-gcc}} python3\n \n \t# Starting with Ubuntu 25.10, sudo can now be provided via either\n \t# sudo(1) or sudo-rs(1), with the latter being the default. The problem\ndiff --git a/ci/lib.sh b/ci/lib.sh\nindex d99e7b9da1..3ec10488d4 100755\n--- a/ci/lib.sh\n+++ b/ci/lib.sh\n@@ -335,16 +335,7 @@ esac\n \n case \"$distro\" in\n ubuntu-*)\n-\t# Python 2 is end of life, and Ubuntu 23.04 and newer don't actually\n-\t# have it anymore. We thus only test with Python 2 on older LTS\n-\t# releases.\n-\tif test \"$distro\" = \"ubuntu-20.04\"\n-\tthen\n-\t\tPYTHON_PACKAGE=python2\n-\telse\n-\t\tPYTHON_PACKAGE=python3\n-\tfi\n-\tMAKEFLAGS=\"$MAKEFLAGS PYTHON_PATH=/usr/bin/$PYTHON_PACKAGE\"\n+\tMAKEFLAGS=\"$MAKEFLAGS PYTHON_PATH=/usr/bin/python3\"\n \n \texport GIT_TEST_HTTPD=true\n \n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"555113","messageId":"20261015-pks-ci-housekeeping-v4-8-c2c88f1b198e@pks.im","threadId":"66489","inReplyTo":"20261015-pks-ci-housekeeping-v4-0-c2c88f1b198e@pks.im","subject":"[PATCH v4 8/8] ci: improve reftable test coverage","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-15T06:57:17Z","receivedAt":"2026-10-15T06:57:17Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"The \"linux-reftable\" job exercises Git with reftables as its default\nbackend. But this job is arguably redundant because we already have the\n\"linux-reftable-leaks\" job that exercises reftables with the leak\nsanitizer enabled, and it is unlikely that we will catch any extra bugs\nwith the leak sanitizer disabled.\n\nOne may thus be triggered to just drop the \"linux-reftable\" job in favor\nof the leak-checking variant. But the latter disables a couple of other\ntests that exercise git-p4, git-svn and other tools. Those tools may not\nbe an essential part of Git nowadays, but I don't quite feel comfortable\nwith reducing test coverage.\n\nInstead, adapt the job to run reftables together with SHA256. which is\nan area that we don't have test coverage for.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n .github/workflows/main.yml | 2 +-\n .gitlab-ci.yml             | 2 +-\n ci/run-build-and-tests.sh  | 6 +++++-\n 3 files changed, 7 insertions(+), 3 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex 47f174ed0e..fe8155772a 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -405,7 +405,7 @@ jobs:\n         - jobname: linux-sha256\n           image: ubuntu:rolling\n           cc: clang\n-        - jobname: linux-reftable\n+        - jobname: linux-reftable-sha256\n           image: ubuntu:rolling\n           cc: clang\n         - jobname: linux-feature-testbed\ndiff --git a/.gitlab-ci.yml b/.gitlab-ci.yml\nindex 3e2e6083cb..9b7698a003 100644\n--- a/.gitlab-ci.yml\n+++ b/.gitlab-ci.yml\n@@ -39,7 +39,7 @@ test:linux:\n       - jobname: linux-sha256\n         image: ubuntu:rolling\n         CC: clang\n-      - jobname: linux-reftable\n+      - jobname: linux-reftable-sha256\n         image: ubuntu:rolling\n         CC: clang\n       - jobname: linux-feature-testbed\ndiff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\nindex 611bf6e56d..1c549634e0 100755\n--- a/ci/run-build-and-tests.sh\n+++ b/ci/run-build-and-tests.sh\n@@ -40,7 +40,11 @@ linux-feature-testbed)\n linux-sha256)\n \texport GIT_TEST_DEFAULT_HASH=sha256\n \t;;\n-linux-reftable|linux-reftable-leaks|osx-reftable)\n+linux-reftable-sha256)\n+\texport GIT_TEST_DEFAULT_HASH=sha256\n+\texport GIT_TEST_DEFAULT_REF_STORAGE_FORMAT=reftable\n+\t;;\n+linux-reftable-leaks|osx-reftable)\n \texport GIT_TEST_DEFAULT_REF_STORAGE_FORMAT=reftable\n \t;;\n \n\n-- \n2.56.0.212.g129ede20d9.dirty\n\n\n"},{"id":"555116","messageId":"20261015070605.GA2556608@coredump.intra.peff.net","threadId":"66489","inReplyTo":"20261015-pks-ci-housekeeping-v4-0-c2c88f1b198e@pks.im","subject":"Re: [PATCH v4 0/8] ci: some housekeeping and modernizations","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2026-10-15T07:06:05Z","receivedAt":"2026-10-15T07:06:05Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Oct 15, 2026 at 08:57:09AM +0200, Patrick Steinhardt wrote:\n\n> Changes in v4:\n>   - Make the test in t5004 work both with SHA1 and SHA256 by forcing the\n>     repo to SHA1.\n>   - Link to v3: https://patch.msgid.link/20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im\n\nThanks, the updated patch 1 looks good to me. I think all of my other\ncomments on v3 were things that were either non-issues, or things we\ndecided to address outside of this series.\n\nSo v4 looks good to me.\n\n-Peff\n\n"},{"id":"555120","messageId":"e6550ed3-351c-451e-8740-f9f449e98402@gmail.com","threadId":"66489","inReplyTo":"20261015-pks-ci-housekeeping-v4-3-c2c88f1b198e@pks.im","subject":"Re: [PATCH v4 3/8] ci: drop unused \"linux-clang\" logic","fromName":"Kaartic Sivaraam","fromEmail":"kaartic.sivaraam@gmail.com","sentAt":"2026-10-15T08:36:30Z","receivedAt":"2026-10-15T08:36:30Z","isPatch":true,"sender":{"key":"kaartic.sivaraam@gmail.com","avatar":"https://avatars.githubusercontent.com/u/12448084?v=4"},"body":"On 10/15/26 12:27, Patrick Steinhardt wrote:\n> In d88d727143 (ci: drop linux-clang job, 2023-06-01) we have dropped the\n> \"linux-clang\" job because another job already uses Clang anyway. But we\n> forgot to also drop the logic in \"ci/run-build-and-tests.sh\", so we now\n> have some unused logic in there.\n> > Drop it.\n> > Signed-off-by: Patrick Steinhardt <ps@pks.im>\n> ---\n>   ci/run-build-and-tests.sh | 4 ----\n>   1 file changed, 4 deletions(-)\n> > diff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\n> index bc5058c917..23e87cbbd6 100755\n> --- a/ci/run-build-and-tests.sh\n> +++ b/ci/run-build-and-tests.sh\n> @@ -37,10 +37,6 @@ linux-TEST-vars)\n>   \texport GIT_TEST_CHECKOUT_WORKERS=2\n>   \texport GIT_TEST_PACK_USE_BITMAP_BOUNDARY_TRAVERSAL=1\n>   \t;;\n> -linux-clang)\n> -\texport NO_RUST=UnfortunatelyYes\n> -\texport GIT_TEST_DEFAULT_HASH=sha1\n> -\t;;\n\nI know we're removing this only because we lost the job already 3 years ago. I just wanted to check a bit more on seeing the job had a NO_RUST flag on.\n\nOn some digging, it seems that 32d5b90590 (Enable Rust by default, 2026-04-09) flipped Rust flags of CI jobs and retained NO_RUST only for this job and the linux-musl-meson jobs. That means, we've been having the NO_RUST flag on a Makefile based job that never existed in the first place which is a bit sad. I wonder if we need to fix the intention at least now and slip the NO_RUST flag into one of the other Makefile based jobs? linux-feature-testbed? Or have a separate job for this?\n\nOf course, this is not really a problem with this series per se. So, we can handle it separately if that's preferred.\n\nHappy to hear thoughts either way.\n\n-- \nSivaraam\n\n\n"},{"id":"555125","messageId":"atCdWdE74-4K5aWc@pks.im","threadId":"66489","inReplyTo":"e6550ed3-351c-451e-8740-f9f449e98402@gmail.com","subject":"Re: [PATCH v4 3/8] ci: drop unused \"linux-clang\" logic","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-15T09:31:05Z","receivedAt":"2026-10-15T09:31:05Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Thu, Oct 15, 2026 at 02:06:30PM +0530, Kaartic Sivaraam wrote:\n> On 10/15/26 12:27, Patrick Steinhardt wrote:\n> > In d88d727143 (ci: drop linux-clang job, 2023-06-01) we have dropped the\n> > \"linux-clang\" job because another job already uses Clang anyway. But we\n> > forgot to also drop the logic in \"ci/run-build-and-tests.sh\", so we now\n> > have some unused logic in there.\n> > \n> > Drop it.\n> > \n> > Signed-off-by: Patrick Steinhardt <ps@pks.im>\n> > ---\n> >   ci/run-build-and-tests.sh | 4 ----\n> >   1 file changed, 4 deletions(-)\n> > \n> > diff --git a/ci/run-build-and-tests.sh b/ci/run-build-and-tests.sh\n> > index bc5058c917..23e87cbbd6 100755\n> > --- a/ci/run-build-and-tests.sh\n> > +++ b/ci/run-build-and-tests.sh\n> > @@ -37,10 +37,6 @@ linux-TEST-vars)\n> >   \texport GIT_TEST_CHECKOUT_WORKERS=2\n> >   \texport GIT_TEST_PACK_USE_BITMAP_BOUNDARY_TRAVERSAL=1\n> >   \t;;\n> > -linux-clang)\n> > -\texport NO_RUST=UnfortunatelyYes\n> > -\texport GIT_TEST_DEFAULT_HASH=sha1\n> > -\t;;\n> \n> I know we're removing this only because we lost the job already 3 years ago.\n> I just wanted to check a bit more on seeing the job had a NO_RUST flag on.\n> \n> On some digging, it seems that 32d5b90590 (Enable Rust by default,\n> 2026-04-09) flipped Rust flags of CI jobs and retained NO_RUST only for this\n> job and the linux-musl-meson jobs. That means, we've been having the NO_RUST\n> flag on a Makefile based job that never existed in the first place which is\n> a bit sad. I wonder if we need to fix the intention at least now and slip\n> the NO_RUST flag into one of the other Makefile based jobs?\n> linux-feature-testbed? Or have a separate job for this?\n> \n> Of course, this is not really a problem with this series per se. So, we can\n> handle it separately if that's preferred.\n\nYeah, we probably should fix this. But same as with the other things\nthat we could do while at it I'd prefer to do those in a subsequent\npatch series.\n\nThanks!\n\nPatrick\n\n"},{"id":"555171","messageId":"xmqqv772opkr.fsf@gitster.g","threadId":"66489","inReplyTo":"atBoE11OSvlFIKis@pks.im","subject":"Re: [PATCH v3 0/8] ci: some housekeeping and modernizations","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-15T17:12:36Z","receivedAt":"2026-10-15T17:12:36Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n> Makes sense. I'll keep the base as-is for now. I assume it's less work\n> for you this way with a primed rerere cache.\n\nIt is exactly the same amount of human work with a primed rerere\ncache to resolve, but the conflict that gets autoresolved with\nrerere still stops automation, so overall it slows me down slightly.\n\nHopefully at v3 this topic is mature enough to require no more\nrerolls, so it does not matter ;-)\n\n\n"},{"id":"555179","messageId":"xmqq4iemon3h.fsf@gitster.g","threadId":"66489","inReplyTo":"20261015070605.GA2556608@coredump.intra.peff.net","subject":"Re: [PATCH v4 0/8] ci: some housekeeping and modernizations","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-15T18:06:10Z","receivedAt":"2026-10-15T18:06:10Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King <peff@peff.net> writes:\n\n> On Thu, Oct 15, 2026 at 08:57:09AM +0200, Patrick Steinhardt wrote:\n>\n>> Changes in v4:\n>>   - Make the test in t5004 work both with SHA1 and SHA256 by forcing the\n>>     repo to SHA1.\n>>   - Link to v3: https://patch.msgid.link/20261014-pks-ci-housekeeping-v3-0-04c24e1f480d@pks.im\n>\n> Thanks, the updated patch 1 looks good to me. I think all of my other\n> comments on v3 were things that were either non-issues, or things we\n> decided to address outside of this series.\n>\n> So v4 looks good to me.\n\nYeah, I am especially pleased to see your \"what would happen after\nSHA-256 becomes the default?\" question and updates in response to\nit.\n\nThanks for writing, and reviewing.  Let me mark it for 'next'.\n\n"},{"id":"555246","messageId":"xmqq8q3xirru.fsf@gitster.g","threadId":"66489","inReplyTo":"atCdWdE74-4K5aWc@pks.im","subject":"Re: [PATCH v4 3/8] ci: drop unused \"linux-clang\" logic","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-16T15:33:57Z","receivedAt":"2026-10-16T15:33:57Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n>> On some digging, it seems that 32d5b90590 (Enable Rust by default,\n>> 2026-04-09) flipped Rust flags of CI jobs and retained NO_RUST only for this\n>> job and the linux-musl-meson jobs. That means, we've been having the NO_RUST\n>> flag on a Makefile based job that never existed in the first place which is\n>> a bit sad. I wonder if we need to fix the intention at least now and slip\n>> the NO_RUST flag into one of the other Makefile based jobs?\n>> linux-feature-testbed? Or have a separate job for this?\n>> \n>> Of course, this is not really a problem with this series per se. So, we can\n>> handle it separately if that's preferred.\n>\n> Yeah, we probably should fix this. But same as with the other things\n> that we could do while at it I'd prefer to do those in a subsequent\n> patch series.\n\nI would consider resurrecting the no-rust job is in the same spirit\nas 8/8 to ensure test coverage for reftable by shuffling jobs\naround.  I do not mind seeing it done separately, but it is not too\nbig an effort to throw it into the feature testbed or linux32 job\njust to make sure the system builds without rust, and doing so now\nwould mean we won't forget.  And it is only until rust becomes\nrequired anyway.\n\n"},{"id":"555382","messageId":"atW1q6fAQBpS1r_7@pks.im","threadId":"66489","inReplyTo":"xmqq8q3xirru.fsf@gitster.g","subject":"Re: [PATCH v4 3/8] ci: drop unused \"linux-clang\" logic","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-19T06:16:11Z","receivedAt":"2026-10-19T06:16:11Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Fri, Oct 16, 2026 at 08:33:57AM -0700, Junio C Hamano wrote:\n> Patrick Steinhardt <ps@pks.im> writes:\n> \n> >> On some digging, it seems that 32d5b90590 (Enable Rust by default,\n> >> 2026-04-09) flipped Rust flags of CI jobs and retained NO_RUST only for this\n> >> job and the linux-musl-meson jobs. That means, we've been having the NO_RUST\n> >> flag on a Makefile based job that never existed in the first place which is\n> >> a bit sad. I wonder if we need to fix the intention at least now and slip\n> >> the NO_RUST flag into one of the other Makefile based jobs?\n> >> linux-feature-testbed? Or have a separate job for this?\n> >> \n> >> Of course, this is not really a problem with this series per se. So, we can\n> >> handle it separately if that's preferred.\n> >\n> > Yeah, we probably should fix this. But same as with the other things\n> > that we could do while at it I'd prefer to do those in a subsequent\n> > patch series.\n> \n> I would consider resurrecting the no-rust job is in the same spirit\n> as 8/8 to ensure test coverage for reftable by shuffling jobs\n> around.  I do not mind seeing it done separately, but it is not too\n> big an effort to throw it into the feature testbed or linux32 job\n> just to make sure the system builds without rust, and doing so now\n> would mean we won't forget.  And it is only until rust becomes\n> required anyway.\n\nIt's not, but I've already got a subsequent patch series anyway where\nI'm following up on some of the related topics that were raised in this\nthread. I've queued the change as part of that follow-up.\n\nPatrick\n\n"},{"id":"555457","messageId":"xmqqmrs94fpm.fsf@gitster.g","threadId":"66489","inReplyTo":"atW1q6fAQBpS1r_7@pks.im","subject":"Re: [PATCH v4 3/8] ci: drop unused \"linux-clang\" logic","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-19T20:07:17Z","receivedAt":"2026-10-19T20:07:17Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n>> I would consider resurrecting the no-rust job is in the same spirit\n>> as 8/8 to ensure test coverage for reftable by shuffling jobs\n>> around.  I do not mind seeing it done separately, but it is not too\n>> big an effort to throw it into the feature testbed or linux32 job\n>> just to make sure the system builds without rust, and doing so now\n>> would mean we won't forget.  And it is only until rust becomes\n>> required anyway.\n>\n> It's not, but I've already got a subsequent patch series anyway where\n> I'm following up on some of the related topics that were raised in this\n> thread. I've queued the change as part of that follow-up.\n\nThanks.  Knowing future plans always helps.\n\n\n"}]}