fsck tests: add test for fsck-ing an unknown type

Fix a blindspot in the fsck tests by checking what we do when we
encounter an unknown "garbage" type produced with hash-object's
--literally option.

This behavior needs to be improved, which'll be done in subsequent
patches, but for now let's test for the current behavior.

Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Ævar Arnfjörð Bjarmason 2021-10-01 11:16:37 +02:00 committed by Junio C Hamano
parent 107691cb07
commit 093fffdfbe

View file

@ -865,4 +865,20 @@ test_expect_success 'detect corrupt index file in fsck' '
test_i18ngrep "bad index file" errors
'
test_expect_success 'fsck hard errors on an invalid object type' '
git init --bare garbage-type &&
(
cd garbage-type &&
git hash-object --stdin -w -t garbage --literally </dev/null &&
cat >err.expect <<-\EOF &&
fatal: invalid object type
EOF
test_must_fail git fsck >out 2>err &&
test_cmp err.expect err &&
test_must_be_empty out
)
'
test_done