From 6d67245728bbbc07ad1eeaf5b3c49f64c6bbcd11 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 20 Nov 2013 15:14:20 -0400 Subject: try to recover even if git fsck cannot be coaxed to tell us any bad objects Sometimes git fsck outputs no shas even with --verbose, but fails, due to badly corrupt objects. The best thing to do in this situation is to try to pull and rsync from remotes, hoping that the bad objects will be overwritten. --- test-runner.hs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'test-runner.hs') diff --git a/test-runner.hs b/test-runner.hs index eb40504..cbb37bc 100644 --- a/test-runner.hs +++ b/test-runner.hs @@ -91,7 +91,7 @@ runTest settings damage = withTmpDir "tmprepo" $ \tmpdir -> do case repairstatus of Just True -> TestResult damage repairstatus . Just . not . Git.Fsck.foundBroken - <$> Git.Fsck.findBroken False g + <$> Git.Fsck.findBroken False False g _ -> return $ TestResult damage repairstatus Nothing data TestResult = TestResult -- cgit v1.2.3