aboutsummaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorPatrick Steinhardt <ps@pks.im>2026-02-24 09:45:50 +0100
committerJunio C Hamano <gitster@pobox.com>2026-02-24 07:33:20 -0800
commit38ae87c1ba6b070a4ab69d9ae08c39bcbfcba00c (patch)
tree6e6bd0bf8f077bf441e332313325f0b6860438d0 /t
parent94f5d9f09e3c25a2c1efafcab7697a3387c80b4b (diff)
downloadgit-38ae87c1ba6b070a4ab69d9ae08c39bcbfcba00c.tar.xz
t6500: explicitly use "gc" strategy
The test in t6500 explicitly wants to exercise git-gc(1) and is thus highly specific to the actual on-disk state of the repository and specifically of the object database. An upcoming change modifies the default maintenance strategy to be the "geometric" strategy though, which breaks a couple of assumptions. One fix would arguably be to disable auto-maintenance altogether, as we do want to explicitly verify git-gc(1) anyway. But as the whole test suite is about git-gc(1) in the first place it feels more sensible to configure the default maintenance strategy to be "gc". Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't')
-rwxr-xr-xt/t6500-gc.sh1
1 files changed, 1 insertions, 0 deletions
diff --git a/t/t6500-gc.sh b/t/t6500-gc.sh
index bef472cb8d..ea9aaad470 100755
--- a/t/t6500-gc.sh
+++ b/t/t6500-gc.sh
@@ -11,6 +11,7 @@ test_expect_success 'setup' '
# behavior, make sure we always pack everything to one pack by
# default
git config gc.bigPackThreshold 2g &&
+ git config set --global maintenance.strategy gc &&
test_oid_init
'