Mercurial > hgsubversion
view tests/fixtures/filecase.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 | 3a9d6cd18332 |
children |
line wrap: on
line source
#!/bin/sh # # Generate filecase.svndump # WARNING: this script must be run on a case-sensitive file system # mkdir temp cd temp mkdir project-orig cd project-orig mkdir trunk cd .. svnadmin create testrepo svnurl=file://`pwd`/testrepo svn import project-orig $svnurl -m "init project" svn co $svnurl project cd project/trunk # Test files and directories differing in case only echo a > a echo A > A echo b > b mkdir d echo a > d/a mkdir D echo a > D/a mkdir e echo a > e/a mkdir f echo a > f/a echo F > F svn add a A b d D e f F svn ci -m 'add files' # Rename files and directories, changing only their case svn mv b B svn mv d/a d/A svn mv e E svn ci -m 'change case' cd ../.. svnadmin dump testrepo > ../filecase.svndump