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.

#!/bin/sh
#
# Generate copies.svndump
#

rm -rf temp
mkdir temp
cd temp
mkdir -p import/trunk/dir
echo a > import/trunk/dir/a

svnadmin create testrepo
svnurl=file://`pwd`/testrepo
svn import import $svnurl -m init

svn co $svnurl project
cd project
svn cp trunk/dir trunk/dir2
echo b >> trunk/dir2/a
svn ci -m 'copy/edit trunk/dir/a'
svn up
svn cp trunk/dir2 trunk/dir3
svn ci -m 'copy dir2 to dir3'
svn rm trunk/dir3/a
svn cp trunk/dir2/a trunk/dir3/a
svn ci -m 'copy and remove'
cd ..

svnadmin dump testrepo > ../copies.svndump