Mercurial > hgsubversion
view tests/fixtures/renametagdir.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 | d380e7e4175a |
children |
line wrap: on
line source
#!/bin/sh # inspired by Python r62868 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 'btt' echo a > trunk/a svn add trunk/a svn ci -m 'Add file.' svn up svn cp trunk branches/test svn ci -m 'Branch.' svn up cd .. svn cp -m 'First tag.' $REPO/branches/test@3 $REPO/tags/test-0.1 svn cp -m 'Weird tag.' $REPO/branches/test@3 $REPO/tags/test-0.1/test svn mv -m 'Fix tag pt 1.' $REPO/tags/test-0.1/test $REPO/tags/test-0.1-real svn rm -m 'Remove weird.' $REPO/tags/test-0.1 svn mv -m 'Fix tag pt 2.' $REPO/tags/test-0.1-real $REPO/tags/test-0.1 cd .. svnadmin dump temp/repo > renametagdir.svndump echo echo 'Complete.' echo 'You probably want to clean up temp now.' echo 'Dump in renametagdir.svndump' exit 0