On 25 Feb 2021, Yasuhito FUTATSUKI wrote:
Then, I made patches. It also allows pypy to run the test without
'python'. (A) Replace the shebang line of svneditor.py from
svneditor.py
at running the configure
script. (fix-svneditor-in-test-patch-a.txt) As @PYTHON@ can be
basename only, relative path, or absolute path, "/usr/bin/env"
is still needed.
(B) Make a script to launch svneditor.py using @PYTHON@,
svneditor.sh
at running the configure
scriptt. (fix-svneditor-in-test-patch-b.txt)
If @PYTHON@ is always absolute path, we can use shebang line
without '/usr/bin/env' in patch (A).
On a Debian GNU/Linux system with only 'python3' (no 'python'), I
tried a complete build and 'make check' in each of these three
configurations:
1. No patch (clean r1886938)
2. Your patch A
3. Your patch B
With a clean tree (no patches), there are the expected 4 test
failures:
FAIL: commit_tests.py 48: set revision props during remote
property edit FAIL: prop_tests.py 1: write/read props in wc
only (ps, pl, pdel, pe) FAIL: prop_tests.py 16: property
operations on a URL FAIL: update_tests.py 38: update --accept
automatic conflict resolution
With just Patch A, there are no test failures -- yay!
With just Patch B, there are the same 4 test failures:
FAIL: commit_tests.py 48: set revision props during remote
property edit FAIL: prop_tests.py 1: write/read props in wc
only (ps, pl, pdel, pe) FAIL: prop_tests.py 16: property
operations on a URL FAIL: update_tests.py 38: update --accept
automatic conflict resolution
Do you get similar results?
Best regards,
-Karl
