From bc77fc6e15093a0d071663c075dfc047fd4a2774 Mon Sep 17 00:00:00 2001 From: Patrick Steinhardt Date: Fri, 20 Feb 2026 11:15:10 +0100 Subject: [PATCH] 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 Signed-off-by: Junio C Hamano --- t/t6500-gc.sh | 1 + 1 file changed, 1 insertion(+) 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 '