diff options
| author | Joey Hess <joey@kitenet.net> | 2013-11-20 15:14:20 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-11-20 15:14:20 -0400 |
| commit | 6d67245728bbbc07ad1eeaf5b3c49f64c6bbcd11 (patch) | |
| tree | fb9fbeb6820e46eef37270a60704947e5aad4bed /test-runner.hs | |
| parent | c2cd79e09b5aad1d634c58f5a130654649e25c49 (diff) | |
| download | git-repair-6d67245728bbbc07ad1eeaf5b3c49f64c6bbcd11.tar.gz | |
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.
Diffstat (limited to 'test-runner.hs')
| -rw-r--r-- | test-runner.hs | 2 |
1 files changed, 1 insertions, 1 deletions
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 |