Hello,
First time for me building subversion from sources (Linux). I’ve upgraded a server from 1.9 to 1.10 and things seem ok, but I have just one test from “make check” failing.
I’m just wondering if it’s a problem or it may be ignored.
Followed instructions at http://blog.ashodnakashian.com/2012/11/building-subversion-on-ubuntu-12-10/
First on a test VM installed from scratch, later on production server. Same results.
Please let me know if you need any exact versions / output for anything.
Exact Ubuntu version: 16.04.4 LTS (server, not desktop, so pretty minimalistic).
Extract from tests.log:
START: locks-test
PASS: lt-locks-test 1: test that locks can expire
PASS: lt-locks-test 2: lock only
PASS: lt-locks-test 3: lookup lock by path
PASS: lt-locks-test 4: attach lock
PASS: lt-locks-test 5: get locks
PASS: lt-locks-test 6: basic locking
PASS: lt-locks-test 7: test that locking requires proper credentials
PASS: lt-locks-test 8: test that locking is enforced in final commit step
PASS: lt-locks-test 9: dir propchange can be committed with locked child
PASS: lt-locks-test 10: breaking, stealing, refreshing a lock
PASS: lt-locks-test 11: check out-of-dateness before locking
PASS: lt-locks-test 12: lock multiple paths
PASS: lt-locks-test 13: lock callback error
svn_tests: E200006: Expected error but got SVN_NO_ERROR
FAIL: lt-locks-test 14: lock/unlock when 'write-lock' couldn't be obtained
PASS: lt-locks-test 15: lock parent and it's child
END: locks-test
ELAPSED: locks-test 0:00:03.594386
Extract from fails.log:
[[[
svn_tests: E200006: Expected error but got SVN_NO_ERROR
FAIL: lt-locks-test 14: lock/unlock when 'write-lock' couldn't be obtained
]]]
Thanks for any insight on this.
Regards,
Juan G. Covas
Received on 2018-05-01 09:56:49 CEST