You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Stephen Butler <sb...@elego.de> on 2011/08/31 22:35:00 UTC
lock_tests.py failing over ra-svn
Hi folks,
Is anyone else seeing the following test failures on trunk?
At least one test FAILED, checking /Users/steve/dev/unix-build/svn-trunk/tests.log
FAIL: lock_tests.py 10: verify svn:needs-lock behavior with defunct lock
FAIL: lock_tests.py 15: verify status of stolen lock
FAIL: lock_tests.py 28: verify info path@X or path -rY return repos lock
FAIL: lock_tests.py 32: verify unlocking with wrong lock token
Summary of test results:
39 tests PASSED
4 tests FAILED
In each case (details below) information about a stolen lock is
not received by the client.
I'm on OS X 10.6.8, developer tools 3.2.5. I don't see any
failures over ra-local, serf, or neon. Over ra-svn they're
reproducible. I don't know if this is a Mac issue, since the
buildbot doesn't include tests on OS X.
Anyone have an idea off the bat? If not, I'll try to debug it.
Thanks,
Steve
From the test log:
lock_tests.py 10: verify svn:needs-lock behavior with defunct lock
CMD: svn update svn-test-work/working_copies/lock_tests-10._b --config-dir /Users/steve/dev/unix-build/svn-trunk/subversion/tests/cmdline/svn-test-work/local_tmp/config --password rayjandom --no-auth-cache --username jrandom
<TIME = 0.300464>
Updating 'svn-test-work/working_copies/lock_tests-10._b':
At revision 2.
Upon removal of a defunct lock, a file with 'svn:needs-lock'
was not set back to read-only
lock_tests.py 15: verify status of stolen lock
CMD: svn status -v -u -q svn-test-work/working_copies/lock_tests-15 --config-dir /Users/steve/dev/unix-build/svn-trunk/subversion/tests/cmdline/svn-test-work/local_tmp/config --password rayjandom --no-auth-cache --username jrandom
[...]
Status against revision: 2
=============================================================
Expected 'iota' and actual 'iota' in status tree are different!
=============================================================
EXPECTED NODE TO BE:
=============================================================
* Node name: iota
Path: svn-test-work/working_copies/lock_tests-15/iota
Contents: None
Properties: {}
Attributes: {'status': ' ', 'writelocked': 'T', 'wc_rev': '2'}
Children: None (node is probably a file)
=============================================================
ACTUAL NODE FOUND:
=============================================================
* Node name: iota
Path: svn-test-work/working_copies/lock_tests-15/iota
Contents: None
Properties: {}
Attributes: {'status': ' ', 'writelocked': 'K', 'wc_rev': '2'}
Children: None (node is probably a file)
lock_tests.py 28: verify info path@X or path -rY return repos lock
CMD: svn status -v -u -q svn-test-work/working_copies/lock_tests-28 --config-dir /Users/steve/dev/unix-build/svn-trunk/subversion/tests/cmdline/svn-test-work/local_tmp/config --password rayjandom --no-auth-cache --username jrandom
[...]
=============================================================
Expected 'iota' and actual 'iota' in status tree are different!
=============================================================
EXPECTED NODE TO BE:
=============================================================
* Node name: iota
Path: svn-test-work/working_copies/lock_tests-28/iota
Contents: None
Properties: {}
Attributes: {'status': ' ', 'writelocked': 'T', 'wc_rev': '1'}
Children: None (node is probably a file)
=============================================================
ACTUAL NODE FOUND:
=============================================================
* Node name: iota
Path: svn-test-work/working_copies/lock_tests-28/iota
Contents: None
Properties: {}
Attributes: {'status': ' ', 'writelocked': 'K', 'wc_rev': '1'}
Children: None (node is probably a file)
lock_tests.py 32: verify unlocking with wrong lock token
CMD: svn unlock svn-test-work/working_copies/lock_tests-32/iota --config-dir /Users/steve/dev/unix-build/svn-trunk/subversion/tests/cmdline/svn-test-work/local_tmp/config --password rayjandom --no-auth-cache --username jrandom
<TIME = 0.293960>
'iota' unlocked.
EXPECTED STDERR (regexp):
.*((No lock on path)|(400 Bad Request))
ACTUAL STDERR:
CWD: /Users/steve/dev/unix-build/svn-trunk/subversion/tests/cmdline
EXCEPTION: SVNUnmatchedError
Platform: Darwin 10.8.0 i386
Dependencies:
bdb: 4.7.25
GNU-iconv: 1.13.1
apr: 1.4.5
apr-util: 1.3.12
httpd: 2.2.19
neon: 0.29.6
serf: 1.0.0
cyrus-sasl: 2.1.23
sqlite: 3070603
openssl: 0.9.8r
swig: 1.3.31
python: 2.7.2
perl: 5.8.9
ruby: 1.8.7
Stephen Butler | Senior Consultant
elego Software Solutions GmbH
Gustav-Meyer-Allee 25 | 13355 Berlin | Germany
tel: +49 30 2345 8696 | mobile: +49 163 25 45 015
fax: +49 30 2345 8695 | http://www.elegosoft.com
Geschäftsführer: Olaf Wagner | Sitz der Gesellschaft: Berlin
Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
Re: lock_tests.py failing over ra-svn
Posted by Paul Burba <pt...@gmail.com>.
On Wed, Aug 31, 2011 at 4:35 PM, Stephen Butler <sb...@elego.de> wrote:
> Hi folks,
>
> Is anyone else seeing the following test failures on trunk?
>
> At least one test FAILED, checking /Users/steve/dev/unix-build/svn-trunk/tests.log
> FAIL: lock_tests.py 10: verify svn:needs-lock behavior with defunct lock
> FAIL: lock_tests.py 15: verify status of stolen lock
> FAIL: lock_tests.py 28: verify info path@X or path -rY return repos lock
> FAIL: lock_tests.py 32: verify unlocking with wrong lock token
> Summary of test results:
> 39 tests PASSED
> 4 tests FAILED
Hi Stephen,
Those tests pass for me on Windows with trunk@1163811:
C:\SVN\src-trunk>win-tests.py -d -c --test=lock -u svn://localhost
Starting Debug svnserve.exe
Testing Debug configuration on remote repository svn://localhost.
Running tests in lock_tests.py [1/1]..........................success
At least one test was SKIPPED, checking C:\SVN\src-trunk\Debug\svn-tests.log
SKIP: lock_tests.py 25: svn:needs-lock and svn:executable, part I
SKIP: lock_tests.py 26: svn:needs-lock and svn:executable, part II
Summary of test results:
41 tests PASSED
2 tests SKIPPED
WARNING: no failures, but 'C:\SVN\src-trunk\Debug\svn-fails.log'
exists from a previous run.
Stopping svnserve.exe
Paul
> In each case (details below) information about a stolen lock is
> not received by the client.
>
> I'm on OS X 10.6.8, developer tools 3.2.5. I don't see any
> failures over ra-local, serf, or neon. Over ra-svn they're
> reproducible. I don't know if this is a Mac issue, since the
> buildbot doesn't include tests on OS X.
>
> Anyone have an idea off the bat? If not, I'll try to debug it.
>
> Thanks,
> Steve
>
>
> From the test log:
>
>
> lock_tests.py 10: verify svn:needs-lock behavior with defunct lock
>
> CMD: svn update svn-test-work/working_copies/lock_tests-10._b --config-dir /Users/steve/dev/unix-build/svn-trunk/subversion/tests/cmdline/svn-test-work/local_tmp/config --password rayjandom --no-auth-cache --username jrandom
> <TIME = 0.300464>
> Updating 'svn-test-work/working_copies/lock_tests-10._b':
> At revision 2.
> Upon removal of a defunct lock, a file with 'svn:needs-lock'
> was not set back to read-only
>
>
>
> lock_tests.py 15: verify status of stolen lock
>
> CMD: svn status -v -u -q svn-test-work/working_copies/lock_tests-15 --config-dir /Users/steve/dev/unix-build/svn-trunk/subversion/tests/cmdline/svn-test-work/local_tmp/config --password rayjandom --no-auth-cache --username jrandom
> [...]
> Status against revision: 2
> =============================================================
> Expected 'iota' and actual 'iota' in status tree are different!
> =============================================================
> EXPECTED NODE TO BE:
> =============================================================
> * Node name: iota
> Path: svn-test-work/working_copies/lock_tests-15/iota
> Contents: None
> Properties: {}
> Attributes: {'status': ' ', 'writelocked': 'T', 'wc_rev': '2'}
> Children: None (node is probably a file)
> =============================================================
> ACTUAL NODE FOUND:
> =============================================================
> * Node name: iota
> Path: svn-test-work/working_copies/lock_tests-15/iota
> Contents: None
> Properties: {}
> Attributes: {'status': ' ', 'writelocked': 'K', 'wc_rev': '2'}
> Children: None (node is probably a file)
>
>
> lock_tests.py 28: verify info path@X or path -rY return repos lock
>
> CMD: svn status -v -u -q svn-test-work/working_copies/lock_tests-28 --config-dir /Users/steve/dev/unix-build/svn-trunk/subversion/tests/cmdline/svn-test-work/local_tmp/config --password rayjandom --no-auth-cache --username jrandom
> [...]
> =============================================================
> Expected 'iota' and actual 'iota' in status tree are different!
> =============================================================
> EXPECTED NODE TO BE:
> =============================================================
> * Node name: iota
> Path: svn-test-work/working_copies/lock_tests-28/iota
> Contents: None
> Properties: {}
> Attributes: {'status': ' ', 'writelocked': 'T', 'wc_rev': '1'}
> Children: None (node is probably a file)
> =============================================================
> ACTUAL NODE FOUND:
> =============================================================
> * Node name: iota
> Path: svn-test-work/working_copies/lock_tests-28/iota
> Contents: None
> Properties: {}
> Attributes: {'status': ' ', 'writelocked': 'K', 'wc_rev': '1'}
> Children: None (node is probably a file)
>
>
>
> lock_tests.py 32: verify unlocking with wrong lock token
>
> CMD: svn unlock svn-test-work/working_copies/lock_tests-32/iota --config-dir /Users/steve/dev/unix-build/svn-trunk/subversion/tests/cmdline/svn-test-work/local_tmp/config --password rayjandom --no-auth-cache --username jrandom
> <TIME = 0.293960>
> 'iota' unlocked.
> EXPECTED STDERR (regexp):
> .*((No lock on path)|(400 Bad Request))
> ACTUAL STDERR:
> CWD: /Users/steve/dev/unix-build/svn-trunk/subversion/tests/cmdline
> EXCEPTION: SVNUnmatchedError
>
>
> Platform: Darwin 10.8.0 i386
>
> Dependencies:
> bdb: 4.7.25
> GNU-iconv: 1.13.1
> apr: 1.4.5
> apr-util: 1.3.12
> httpd: 2.2.19
> neon: 0.29.6
> serf: 1.0.0
> cyrus-sasl: 2.1.23
> sqlite: 3070603
> openssl: 0.9.8r
> swig: 1.3.31
> python: 2.7.2
> perl: 5.8.9
> ruby: 1.8.7
>
>
> Stephen Butler | Senior Consultant
> elego Software Solutions GmbH
> Gustav-Meyer-Allee 25 | 13355 Berlin | Germany
> tel: +49 30 2345 8696 | mobile: +49 163 25 45 015
> fax: +49 30 2345 8695 | http://www.elegosoft.com
> Geschäftsführer: Olaf Wagner | Sitz der Gesellschaft: Berlin
> Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>
>
>
Re: lock_tests.py failing over ra-svn
Posted by Stephen Butler <sb...@elego.de>.
On Aug 31, 2011, at 23:47 , Stefan Sperling wrote:
> On Wed, Aug 31, 2011 at 10:35:00PM +0200, Stephen Butler wrote:
>> Hi folks,
>>
>> Is anyone else seeing the following test failures on trunk?
>>
>> At least one test FAILED, checking /Users/steve/dev/unix-build/svn-trunk/tests.log
>> FAIL: lock_tests.py 10: verify svn:needs-lock behavior with defunct lock
>> FAIL: lock_tests.py 15: verify status of stolen lock
>> FAIL: lock_tests.py 28: verify info path@X or path -rY return repos lock
>> FAIL: lock_tests.py 32: verify unlocking with wrong lock token
>> Summary of test results:
>> 39 tests PASSED
>> 4 tests FAILED
>>
>> In each case (details below) information about a stolen lock is
>> not received by the client.
>>
>> I'm on OS X 10.6.8, developer tools 3.2.5. I don't see any
>> failures over ra-local, serf, or neon. Over ra-svn they're
>> reproducible. I don't know if this is a Mac issue, since the
>> buildbot doesn't include tests on OS X.
>
> Do you see these with 1.7.x, too?
>
> (Please say "no" ;)
No. I mean, really no. ;) There were no failures when I tested 1.7.0-rc2
last week (after I resolved some build problems on my laptop, which took
a while.)
Steve
--
Stephen Butler | Senior Consultant
elego Software Solutions GmbH
Gustav-Meyer-Allee 25 | 13355 Berlin | Germany
tel: +49 30 2345 8696 | mobile: +49 163 25 45 015
fax: +49 30 2345 8695 | http://www.elegosoft.com
Geschäftsführer: Olaf Wagner | Sitz der Gesellschaft: Berlin
Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
Re: lock_tests.py failing over ra-svn
Posted by Stefan Sperling <st...@elego.de>.
On Wed, Aug 31, 2011 at 10:35:00PM +0200, Stephen Butler wrote:
> Hi folks,
>
> Is anyone else seeing the following test failures on trunk?
>
> At least one test FAILED, checking /Users/steve/dev/unix-build/svn-trunk/tests.log
> FAIL: lock_tests.py 10: verify svn:needs-lock behavior with defunct lock
> FAIL: lock_tests.py 15: verify status of stolen lock
> FAIL: lock_tests.py 28: verify info path@X or path -rY return repos lock
> FAIL: lock_tests.py 32: verify unlocking with wrong lock token
> Summary of test results:
> 39 tests PASSED
> 4 tests FAILED
>
> In each case (details below) information about a stolen lock is
> not received by the client.
>
> I'm on OS X 10.6.8, developer tools 3.2.5. I don't see any
> failures over ra-local, serf, or neon. Over ra-svn they're
> reproducible. I don't know if this is a Mac issue, since the
> buildbot doesn't include tests on OS X.
Do you see these with 1.7.x, too?
(Please say "no" ;)