view tests/fixtures/executebit.sh @ 1450:3c4fbf59e503

svnmeta: do not add instance references to the class object This is part of a bigger plan to prevent a fd leak by making sure the sqlite connection object is garbage collected. Usually this is not a very serious issue but the testing framework will run all tests in a single process by default. The fd leak will make tests fail on systems with a low RLIMIT_NOFILE. Previously, when we are adding new properties to the SVNMeta class, we bind the current instance in the closure, which essentially prevents any SVNMeta instances from being garbage collected (and its state like revmap). This patch changed "self" from the closure one to the lambda argument to address the issue.
author Jun Wu <quark@fb.com>
date Fri, 27 May 2016 01:42:55 +0100
parents c35f59aa200e
children
line wrap: on
line source

#!/bin/sh
#
# Generate executebit.svndump
#

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
echo text > text1
echo text > text2
touch empty1
touch empty2
python -c "file('binary1', 'wb').write('a\x00b')"
python -c "file('binary2', 'wb').write('a\x00b')"
svn add text1 text2 binary1 binary2 empty1 empty2
svn propset svn:mime-type application/octet-stream binary1 binary2
svn propset svn:executable yes binary1 text1 empty1
svn ci -m init
# switch exec properties
svn propdel svn:executable binary1 text1 empty1
svn propset svn:executable yes binary2 text2 empty2
svn ci -m changeexec
cd ../..

svnadmin dump testrepo > ../executebit.svndump