Hi everyone! This patch was created in response to something we observed in Google, where fsck failed to detect that the commit graph was invalid. We initially assumed that fsck never checked the commit graph, but it turns out that it does so only when core.commitgraph is set, even though we set defaults for "whether to use the commit graph" in the repository settings. Instead of using the config, let's use repository settings where available. Replace core.commitGraph and core.multiPackIndex with their equivalent repository settings in fsck and gc. v5 is based off Ævar's fix (commit-graph: make "verify" work with replace refs, [1]). As Ævar noted in v4, the mktag test failures indicated buggy behavior "git commit-graph verify" when replace refs are enabled, so we should fix the bug instead of just disabling commit-graph. Ævar, Derrick, thanks for the productive discussion, I feel like I understand this area a little better now. Barring any unseen bugs, this should be ready to merge. [1] https://lore.kernel.org/git/cover-0.3-00000000000-20211014T233343Z-avarab@xxxxxxxxx/ Changes since v4 * Rebase onto [1], which fixes a bug with commit-graph verify with replace refs enabled. * Remove GIT_TEST_COMMIT_GRAPH=0 in t3800-mktag.sh because the bug that it was covering up is now fixed. Changes since v3 * Disable GIT_TEST_COMMIT_GRAPH in tests that intentionally corrupt things in a way that is incompatible with commit-graphs. * Make patch 1 and 2's commit messages more concise (thanks Ævar!). Changes since v2: * Various small test fixes (thanks Eric!). Most notably, I've used -c instead of test_config because test_config can affect the values in subsequent tests. * Rewording fix in patch 3 commit message * Refactor tests in patch 3 so that we use a single helper function instead of copy-pasted code Changes since v1: * clean up typo in patch 1 commit message * document the commits that patches 1 and 2 address * use test helpers in patch 1 * rewrite patch 2's tests so that it's easier to tell that each test does something different * reword patch 3 commit message to explain the bug * add tests to patch 3 Glen Choo (3): fsck: verify commit graph when implicitly enabled fsck: verify multi-pack-index when implictly enabled gc: perform incremental repack when implictly enabled builtin/fsck.c | 5 +++-- builtin/gc.c | 5 ++--- t/t0410-partial-clone.sh | 6 +++++- t/t5318-commit-graph.sh | 23 ++++++++++++++++++++++- t/t5319-multi-pack-index.sh | 5 ++++- t/t7900-maintenance.sh | 28 ++++++++++++++++++++++++---- 6 files changed, 60 insertions(+), 12 deletions(-) Range-diff against v4: 1: aac1253e7b ! 1: 567d40849a fsck: verify commit graph when implicitly enabled @@ Commit message Add tests to "t5318-commit-graph.sh" to verify that fsck checks the commit-graph as expected for the 3 values of core.commitGraph. Also, - disable GIT_TEST_COMMIT_GRAPH for tests that use fsck in ways that - assume that commit-graph checking is disabled (t/t3800-mktag.sh, - t/t0410-partial-clone.sh). + disable GIT_TEST_COMMIT_GRAPH in t/t0410-partial-clone.sh because some + test cases use fsck in ways that assume that commit-graph checking is + disabled. Helped-by: Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> Signed-off-by: Glen Choo <chooglen@xxxxxxxxxx> @@ t/t0410-partial-clone.sh: test_expect_success 'rev-list stops traversal at missi ! grep $FOO out ' - ## t/t3800-mktag.sh ## -@@ t/t3800-mktag.sh: test_description='git mktag: tag object verify test' - - . ./test-lib.sh - -+# When enabled, some commands will automatically write commit-graphs. -+# This will cause the mktag tests to fail because fsck will attempt to -+# verify the out-of-sync commit graph. -+GIT_TEST_COMMIT_GRAPH=0 -+ - ########################################################### - # check the tag.sig file, expecting verify_tag() to fail, - # and checking that the error message matches the pattern - ## t/t5318-commit-graph.sh ## @@ t/t5318-commit-graph.sh: test_expect_success 'detect incorrect chunk count' ' $GRAPH_CHUNK_LOOKUP_OFFSET 2: ed64983430 = 2: 7cb44a7aeb fsck: verify multi-pack-index when implictly enabled 3: 821b492d8b = 3: a436c45af7 gc: perform incremental repack when implictly enabled -- 2.33.0.1079.g6e70778dc9-goog
