view tests/fixtures/spaces-in-path.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 a739568f8d48
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 tags
mkdir tags/versions
mkdir tags/blah
svn add *
svn ci -m 'btt'
cd trunk
for a in alpha beta gamma delta ; do
    echo $a > $a
    svn add $a
done
svn ci -m 'Add files.'

echo 'foo bar' > 'foo bar'
svn add 'foo bar'
svn ci -m 'Add files.'

mkdir 'blah blah'
echo 'another file' > 'blah blah/another file'
svn add 'blah blah'
svn ci -m 'Add files.'

cd ..
svn up
svn cp trunk branches/dev_branch
svn ci -m 'Make a branch'
cd ../..

svnadmin dump temp/repo > spaces-in-path.svndump
echo
echo 'Complete.'
echo 'You probably want to clean up temp now.'
echo 'Dump in spaces-in-path.svndump'
exit 0