-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is run-test.py itself broken? #20
Comments
After updating svntest/ by copying from Subversion's source tree (trunk, r1895425), '
Is it need to run the test that Subversion older than 1.9? |
It turned out that run-test.py uses 'bdb' type fs in Subversion repos. With updated svntest tree and Subversion trunk(r1895939) binaries built with bdb support (although it is deprecated), I could run run-test.py successfully with ' Without updated svntest and Subversion trunk(r1895939) binaries built with bdb support, the result is just same as top comment. Anyways, it seems some modification in test suites is needed to run it on environments nowadays. |
On Scientific Linux with Subversion 1.9.7 and Python 2.7 environment, run-test.py with latest svntest (r1895939) shows exception like #20 (comment) but ' However, with svntest on Subversion 1.9.7 (built with bdb support), I could run ' |
This was incorrect. It was caused by embeded If I overwrited the value with I'll make a PR. |
…owadays. * svntest/__init__.py, svntest/actions.py, svntest/factory.py, svntest/main.py, svntest/objects.py, svntest/sandbox.py, svntest/testcase.py, svntest/tree.py, svntest/verify.py, svntest/wc.py: Update the svntest subdirectory from http://svn.apache.org/repos/asf/subversion/trunk/subversion/tests/cmdline/svntest using svntest/update.sh. Adjust run-tests.py for changes in svntest. * runtest.py: - Adjust required version of Python 2. - Get the minor version of installed svn program and set it to svntest.main.SVN_VER_MINOR. This allows at least Subversion >= 1.9 to run the test suites.
When I ran '
python2.7 ./run-test.py
' I always got:on FreeBSD 13 with Subversion 1.14.1, CentOS 7 with Subversion 1.14.1 and Scientific Linux with Subversion 1.9.7.
Even after I modified run-test.py with patch below, the behaiviour is not changed.
Are there something wrong in my usage of run-test.py? Or is run-test.py itself broken now?
The text was updated successfully, but these errors were encountered: