[PATCH v6 02/22] fsck tests: add test for fsck-ing an unknown type
From: Ævar Arnfjörð Bjarmason <hidden>
Date: 2021-09-07 10:58:30
Subsystem:
the rest · Maintainer:
Linus Torvalds
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 <redacted> --- t/t1450-fsck.sh | 12 ++++++++++++ 1 file changed, 12 insertions(+)
diff --git a/t/t1450-fsck.sh b/t/t1450-fsck.sh
index 7becab5ba1e..f10d6f7b7e8 100755
--- a/t/t1450-fsck.sh
+++ b/t/t1450-fsck.sh@@ -863,4 +863,16 @@ 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 && + empty_blob=$(git -C garbage-type hash-object --stdin -w -t blob </dev/null) && + garbage_blob=$(git -C garbage-type hash-object --stdin -w -t garbage --literally </dev/null) && + cat >err.expect <<-\EOF && + fatal: invalid object type + EOF + test_must_fail git -C garbage-type fsck >out.actual 2>err.actual && + test_cmp err.expect err.actual && + test_must_be_empty out.actual +' + test_done
--
2.33.0.815.g21c7aaf6073