On Wed, 1 Feb 2006, Kamesh Jayachandran wrote:
> Hi Karl,
>
> Yes same 16 Test Case failures for make svnsshcheck with and without my
> changes.
> Here are they.
> FAIL: commit_tests.py 34: post commit hook failure case testing
> FAIL: switch_tests.py 16: relocate with prefixes longer than repo root
> FAIL: stat_tests.py 17: status output in XML format
> FAIL: blame_tests.py 4: blame output in XML format
> FAIL: lock_tests.py 1: lock a file and verify that it's locked
> FAIL: lock_tests.py 7: examine the fields of a lockfile for correctness
> FAIL: svnsync_tests.py 1: copy and modify
> FAIL: svnsync_tests.py 2: copy from previous version and modify
> FAIL: svnsync_tests.py 3: copy from previous version
> FAIL: svnsync_tests.py 4: modified in place
> FAIL: svnsync_tests.py 5: tag empty trunk
> FAIL: svnsync_tests.py 6: tag trunk containing a sub-directory
> FAIL: svnsync_tests.py 7: tag trunk containing a file (#2)
> FAIL: svnsync_tests.py 8: tag trunk containing a file
> FAIL: svnsync_tests.py 9: tag with a modified file
> FAIL: svnsync_tests.py 10: directory property changes
>
I *think* I've seen this list before:-) Just a guess: are you running
svnserve under a non-C locale (i.e. with translated error messages)? If
so, test that depend on the wording of specific error messages that are
generated on the server side will fail.
Thanks,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 1 21:23:22 2006