Juan Gabriel Covas <jgco...@softline.es> writes:
> 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
> ]]]
That's odd. You can run just that one test:
cd subversion/tests/libsvn_fs
./fs-test 14
Does it always fail? What sort of filesystem are you using? Is it a
network filesystem?
If you have strace installed you can run:
libtool --mode=execute strace ./locks-test 14 2>&1 | grep failure/write-lock
For a successful test the output should end:
chmod("test-obtain-write-lock-failure/write-lock", 0444) = 0
open("test-obtain-write-lock-failure/write-lock", O_RDWR|O_CLOEXEC) = -1
EACCES (Permission denied)
open("test-obtain-write-lock-failure/write-lock", O_RDWR|O_CLOEXEC) = -1
EACCES (Permission denied)
When the test is working it makes the "write-lock" file readonly (the
chmod) and then two attempts to open it fail. In your case it appears
that the attempts to open the file do not fail.
--
Philip
