Patrick Steinhardt's series follows earlier CI housekeeping discussions and is built on the 9th batch of the cycle. It consolidates test-environment setup, always sets GIT_TEST_USE_SET_E on Linux jobs, deduplicates variables by pattern matching, merges job-name switches, makes tests honor the default ref storage format, and adds a NO_RUST build using glibc.

Phillip Wood reviewed the whole diff and found it nice. He welcomed moving all job-dependent variable assignments into ci/lib.sh and removing the linux-reftable-sha256 job while keeping coverage. He thought disabling Rust in the sanitizer job makes sense because that job checks C code, though the balance might shift if Git gains more unsafe Rust.

The final patch adds a "--feature-testbed" toggle to the test suite. It sets the GIT_TEST_* variables of the "feature-testbed" CI job, so developers can reproduce that job locally and CI has a single source of truth. Wood suggested the commit message mention that the CI job also sets OPENSSL_SHA1_UNSAFE, which the toggle does not, because the toggle only covers GIT_TEST_* variables.

Jeff King found patches 1-7 obviously good and is lukewarm on the last, though he can live with it. He said the feature would only half work if the culprit is a build flag, and that the complexity may not be worth it. If it is kept, he asked whether it should be "make FEATURE_TESTBED=1", enabling the right build knobs, with test-lib.sh reading the variable from BUILD-OPTIONS.

Junio C Hamano praised the simplicity of one approach and thanked the reviewers. He also said one shell helper should quote the right-hand side, for example eval "$1=\"\$2\"", because CodingGuidelines notes buggy shells even though POSIX does not require the quoting.