diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-05-23 11:23:30 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-05-23 11:23:30 -0400 |
| commit | 81d9661e081a7ca11f4bf5547ffe180071fd81ef (patch) | |
| tree | a26b088710ca161d686e7c9d44bbc9c3574f4aa2 /Test.hs | |
| parent | 6b5d235b83f9d31fb633354ba12d7d5ff4dcb9c2 (diff) | |
fix recent test suite reversion
git annex adjust --force will overwrite any current adjusted branch.
I didn't document this because for the user, deleting the branch is just as
good.
Diffstat (limited to 'Test.hs')
| -rw-r--r-- | Test.hs | 10 |
1 files changed, 6 insertions, 4 deletions
@@ -1062,10 +1062,12 @@ test_conflict_resolution_adjusted_branch = whenM Annex.AdjustedBranch.isGitVersi writeFile conflictor "conflictor2" add_annex conflictor @? "add conflicter failed" git_annex "sync" [] @? "sync failed in r2" - unlessM (annexeval Config.isDirect) $ do - -- need v6 to use adjust - git_annex "upgrade" [] @? "upgrade failed" - git_annex "adjust" ["--unlock"] @? "adjust failed" + -- need v6 to use adjust + git_annex "upgrade" [] @? "upgrade failed" + -- We might be in an adjusted branch + -- already, when eg on a crippled + -- filesystem. So, --force it. + git_annex "adjust" ["--unlock", "--force"] @? "adjust failed" pair r1 r2 forM_ [r1,r2,r1] $ \r -> indir r $ git_annex "sync" [] @? "sync failed" |