Mercurial > hgsubversion
view tests/fixtures/invalid_utf8.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 | 312f36a425f0 |
children |
line wrap: on
line source
#!/bin/bash #-*- coding: utf-8 -*- # # Generate invalid_utf8.svndump # #check svnadmin version, must be >= 1.7 SVNVERSION=$(svnadmin --version | head -n 1 | cut -d \ -f 3) if [[ "$SVNVERSION" < '1.7' ]] ; then echo "You MUST have svn 1.7 or above to use this script" exit 1 fi set -x TMPDIR=$(mktemp -d) WD=$(pwd) cd $TMPDIR svnadmin create failrepo svn co file://$PWD/failrepo fail ( cd fail touch A svn add A svn ci -m blabargrod ) svnadmin --pre-1.6-compatible create invalid_utf8 svnadmin dump failrepo | \ sed "s/blabargrod/$(echo blåbærgrød | iconv -f utf-8 -t latin1)/g" | \ svnadmin load --bypass-prop-validation invalid_utf8 tar cz -C invalid_utf8 -f "$WD"/invalid_utf8.tar.gz .