subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko Čibej <br...@apache.org>
Subject Re: locks-test fail when building subversion-1.10.0 from sources under Linux (Ubuntu 16)
Date Tue, 01 May 2018 12:08:23 GMT
On 01.05.2018 13:43, Juan Gabriel Covas wrote:
>
>  
>
> 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…
>


This is extremely strange. Your filesystem appears to be seriously
broken ... it should be impossible to open a read-only file in write
mode. Are you absolutely sure that you're running the tests on /dev/sda1?

Perhaps the chmod() is failing ... what are the actual permissions on
that file when the test has completed?

-- Brane


Mime
View raw message