view tests/fixtures/project_name_with_space.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 c421e6bf0d95
children
line wrap: on
line source

#!/bin/sh
mkdir temp
cd temp
svnadmin create repo
svn co file://`pwd`/repo wc
cd wc
mkdir 'project name'
cd 'project name'
mkdir branches trunk tags
cd ..
svn add *
svn ci -m 'btt'

cd 'project name'/trunk
for a in alpha beta gamma delta ; do
    echo $a > $a
    svn add $a
done
svn ci -m 'Add files.'

mkdir al
echo foo > al/foo
svn add al
svn ci -m 'add directory al'

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

cd branches/dev_branch
svn rm delta
echo narf > alpha
echo iota > iota
svn add iota
svn ci -m 'branch changes'

cd ../../../../..
svnadmin dump temp/repo > project_name_with_space.svndump

echo
echo 'Complete.'
echo 'You probably want to clean up temp now.'
echo 'Dump in project_name_with_space.svndump'

exit 0