Mercurial > hgsubversion
view tests/fixtures/pushexternals.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 | 2412800b1258 |
children |
line wrap: on
line source
#!/bin/sh # # Generate pushexternals.svndump # mkdir temp cd temp mkdir project-orig cd project-orig mkdir trunk mkdir externals cd .. svnadmin create testrepo svnurl=file://`pwd`/testrepo svn import project-orig $svnurl -m "init project" svn co $svnurl project cd project/externals mkdir project1 echo a > project1/a svn add project1 mkdir project2 echo a > project2/b svn add project2 svn ci -m "configure externals projects" cd ../trunk echo a > a # dir is used to set svn:externals on an already existing directory mkdir dir svn add a dir svn ci -m "add a and dir" svn rm a svn ci -m "remove a" cd ../.. svnadmin dump testrepo > ../pushexternals.svndump