Mercurial > hgsubversion
view tests/fixtures/emptyrepo2.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 | f9014e28721b |
children |
line wrap: on
line source
#!/bin/sh # # Create emptyrepo2.svndump # # The generated repository contains a sequence of empty revisions # created with a combination of svnsync and filtering mkdir temp cd temp mkdir project-orig cd project-orig mkdir -p sub/trunk other echo a > other/a cd .. svnadmin create testrepo svnurl=file://`pwd`/testrepo svn import project-orig $svnurl -m init svn co $svnurl project cd project echo a >> other/a svn ci -m othera echo a >> other/a svn ci -m othera2 echo b > sub/trunk/a svn add sub/trunk/a svn ci -m adda cd .. svnadmin create testrepo2 cat > testrepo2/hooks/pre-revprop-change <<EOF #!/bin/sh exit 0 EOF chmod +x testrepo2/hooks/pre-revprop-change svnurl2=file://`pwd`/testrepo2 svnsync init --username svnsync $svnurl2 $svnurl/sub svnsync sync $svnurl2 svnadmin dump testrepo2 > ../emptyrepo2.svndump