Mercurial > hgsubversion
view tests/fixtures/branch_prop_edit.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 | cf6fe8457570 |
children |
line wrap: on
line source
#!/bin/sh mkdir temp cd temp svnadmin create repo svn co file://`pwd`/repo wc cd wc mkdir branches trunk svn add * svn ci -m 'branches trunk' svn up cd trunk for a in alpha beta gamma ; do echo $a > $a svn add $a done svn ci -m 'Files.' cd .. svn up svn cp trunk branches/dev_branch svn ci -m 'make a branch' svn up cd branches/dev_branch echo epsilon > epsilon svn add epsilon svn ci -m 'Add a file on the branch.' svn up cd ../.. cd branches/dev_branch svn ps 'svn:ignore' 'delta' . svn ci -m 'Commit bogus propchange.' svn up cd ../../.. pwd svnadmin dump repo > ../branch_prop_edit.svndump cd .. echo 'Dump created in branch_prop_edit.svndump. You can probably delete temp.' exit 0