On Tuesday, December 10, 2002, at 04:05 PM, Greg Hudson wrote:
>> Most of the tests pass until I get to diff_test 5 which never
>> completes
>
> diff_tests 5 tests a code path which opens two connections to the
> repository ("svn diff -r 3:4 url"). So it will expose any
> single-threadedness problem on the server side. In daemon mode, right
> now you're single-threaded if APR_HAS_FORK isn't defined; in ssh mode,
> a
> single-threadedness could be the result of an sshd problem (though I've
> never heard of anything like that) or a Berkeley db locking problem.
A BDB locking problem was my take too (especially since I vaguely
remember BDB 4.0 was known to have some locking problems on MacOS X).
Does anyone know how to go about tracking this down?
>> I just tried using 'svnserve -d' and no ssh tunnelling. This time the
>> load dropped to 0 inside update_tests.py. tests.log reveals:
>
> I can't explain that one. I'll try to verify tonight that daemon-mode
> ra_svn passes the test suite, though I'll be trying on Linux, not MacOS
> X.
I was surprised too. I was especially surprised since the same test
passes when using ssh tunnelling.
Be well,
Will :-}
P.S. If the problem is with the MacOS server code, I'd be interested
in trying with a linux server and a MacOS client. Any thoughts on how
you might run 'make check' in this situation? i.e. I'd be able to run
'make check' on the server to verify that the linux client and server
were both correct, but is there a way to check the MacOS client without
worrying about the MacOS server?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 10 06:24:06 2002