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 18:32:51 GMT
On 01.05.2018 20:13, Juan Gabriel Covas wrote:
>
>  
>
>  
>
> Ok, my mistake.
>
>  
>
> >>> SUMMARY: All tests successful.
>
>  
>
> I got “success” for all the tests from “make check” command after
> compiling svn from sources NOT using the root account.
>
>  
>
> First I tried to ensure the build process was using the “apr” and
> “apr-util” compiled from the subversion-1.10 sources directory, but
> the same locks-test #14 failed (even forced a “apt-get remove libapr1
> libapr1-dev libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-dev
> libaprutil1-ldap”).
>
>  
>
> But that was not the problem. Only when I used a non-root account to
> compile from sources from scratch, all the tests were successfull.
>
>  
>
> Regards and sorry for the inconvenience,
>


Well, well. This does explain the test failure.

But let me give you a hint: Compiling sources as 'root' is, to put it
mildly, just a "bit" dangerous. What if I added an 'rm -rf /' to our
build scripts? By mistake, of course, obviously I'd never do that on
purpose (even if it /would/ be very educational).

-- Brane

 
>
> Philip said:
>
> >If you have gdb installed you can check whether the 0444 permissions
>
> >have made it to the filesystem (-r--r--r--).  Something like:
>
>  
>
>   $ libtool --mode=execute gdb -arg ./locks-test 14
>
>   (gdb) b svn_fs_lock_many
>
>   (gdb) r
>
>   Breakpoint 1
>
>   (gdb) shell ls -l test-obtain-write-lock-failure/write-lock
>
>   -r--r--r-- 1 pm pm 0 May  1 13:17
> test-obtain-write-lock-failure/write-lock
>
>   (gdb) b open
>
>   (gdb) c
>
>   Breakpoint 2
>
>   (gdb) shell ls -l test-obtain-write-lock-failure/write-lock
>
>   -r--r--r-- 1 pm pm 0 May  1 13:17
> test-obtain-write-lock-failure/write-lock
>
>   (gdb) fin
>
>   (gdb) fin
>
>   Value returned is $1 = 13
>
>   (gdb) p fname_apr
>
>   $2 = 0x7ffff7eea130 "test-obtain-write-lock-failure/write-lock"
>
>   (gdb) shell ls -l test-obtain-write-lock-failure/write-lock
>
>   -r--r--r-- 1 pm pm 0 May  1 13:17
> test-obtain-write-lock-failure/write-lock
>
>  
>
> >The second breakpoint is the open that should fail.  The two "fin"
>
> >commands return to the Subversion code and the value 13 is EPERM >showing
>
> >the open failed (because the file has permissions -r--r--r--).
>
>  
>
> >In your case I assume the return value is 0 rather than 13 and the file
>
> >permissions are not -r--r--r--.
>
>  
>


Mime
View raw message