Mercurial > hgsubversion
view tests/fixtures/rename_tag_test.sh @ 1539:0ebcc5bbf692
tests: when making a `memctx`, make sure to use a single repo instance
The way self.repo is dynamic produces bad lock behavior because the
`context.memctx` ends up with a different instance than self in
`localrepo.commitctx`, which means the callbacks in the `memctx` get
an unlocked repo instance. This causes lock warning failures. When
it's not a code freeze for core, we should probably:
* Make lock failures hard, not just warnings
* Stop holding a repo reference in memctx, or otherwise check it's the same
instance as `self` during `localrepo.commitctx`
That's my best guess based on the (very hard to debug) test failures here.
| author | Augie Fackler <raf@durin42.com> |
|---|---|
| date | Sat, 28 Oct 2017 21:34:52 -0400 |
| parents | 76e9504db03b |
| children |
line wrap: on
line source
#!/bin/sh mkdir temp cd temp svnadmin create repo svn co file://`pwd`/repo wc export REPO=file://`pwd`/repo cd wc mkdir branches trunk tags svn add * svn ci -m 'Empty dirs.' echo 'file: alpha' > trunk/alpha svn add trunk/alpha svn ci -m 'Add alpha' svn up echo 'Data of beta' > trunk/beta svn add trunk/beta svn ci -m 'Add beta' svn up cd .. svn cp -m 'tagging r3' $REPO/trunk@3 $REPO/tags/tag_r3 svn cp -m 'tag from a tag' $REPO/tags/tag_r3 $REPO/tags/copied_tag svn mv -m 'rename a tag' $REPO/tags/copied_tag $REPO/tags/other_tag_r3 cd .. svnadmin dump temp/repo > rename_tag_test.svndump echo echo 'Complete.' echo 'You probably want to clean up temp now.' echo 'Dump in renametagdir.svndump' exit 0