Junio C Hamano <gitster@xxxxxxxxx> writes: > It does seem that this topic directly queued on 'master' by itself > without any other topics do break the CI quite badly. Almost > nothing passes: > > https://github.com/git/git/actions/runs/5812873987 > > but it may be something as silly as failing test lint. I didn't > check very closely. And a bit further digging reveals that it is the case. https://github.com/git/git/actions/runs/5812873987/job/15759211568#step:4:787 Locally you should be able to reproduce it by make make -C t test-lint before sending your patches out. I've queued a squashable fix-up on top of the topic. Thanks. --- t/t7700-repack.sh | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/t/t7700-repack.sh b/t/t7700-repack.sh index 9b1e189a62..48e92aa6f7 100755 --- a/t/t7700-repack.sh +++ b/t/t7700-repack.sh @@ -342,8 +342,9 @@ test_expect_success 'repacking with a filter works' ' ' test_expect_success '--filter fails with --write-bitmap-index' ' - GIT_TEST_MULTI_PACK_INDEX_WRITE_BITMAP=0 test_must_fail git -C bare.git repack \ - -a -d --write-bitmap-index --filter=blob:none + test_must_fail \ + env GIT_TEST_MULTI_PACK_INDEX_WRITE_BITMAP=0 \ + git -C bare.git repack -a -d --write-bitmap-index --filter=blob:none ' test_expect_success 'repacking with two filters works' ' -- 2.42.0-rc1
