subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Juan Gabriel Covas <jgco...@softline.es>
Subject RE: locks-test fail when building subversion-1.10.0 from sources under Linux (Ubuntu 16)
Date Tue, 01 May 2018 11:43:32 GMT

Thanks for your input.

>> 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

Result:

# ./fs-test 14
PASS:  lt-fs-test 14: set/get txn props, commit, validate new rev props

>Does it always fail?

Always Pass when executed individually.

>What sort of filesystem are you using?  Is it a
>network filesystem?

No network filesystem:
# mount | grep sda1
/dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)

>If you have strace installed you can run:
>  libtool --mode=execute strace ./locks-test 14 2>&1 | grep failure/write-lock

This is what I get:

…/libsvn_fs# libtool --mode=execute strace ./locks-test 14 2>&1 | grep failure/write-lock

unlink("test-obtain-write-lock-failure/write-lock") = 0
open("test-obtain-write-lock-failure/write-lock", O_WRONLY|O_CREAT|O_EXCL|O_CLOEXEC, 0666)
= 3
open("test-obtain-write-lock-failure/write-lock", O_RDWR|O_CLOEXEC) = 3
lstat("test-obtain-write-lock-failure/write-lock", {st_mode=S_IFREG|0644, st_size=0, ...})
= 0
chmod("test-obtain-write-lock-failure/write-lock", 0444) = 0
open("test-obtain-write-lock-failure/write-lock", O_RDWR|O_CLOEXEC) = 3

>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)

Doesn’t seem to be the same…

Juan


Mime
View raw message