On 9/8/06, Paul Burba <paulb@softlanding.com> wrote:
> Garrett,
>
> This may be something you're already aware of, but while running the tests
> on a patch I'm working on, I discovered some DAV test failures on Windows.
> A quick check revealed these failures first appeared in r21332.
>
> I haven't investigated too deeply, but noticed that all but one* of the
> failed tests ended with the following error when attempting an update,
> switch, or checkout:
>
> "svn: REPORT response handling failed to complete the editor drive"
>
> FAIL: basic_tests.py 6: basic corruption detection
> FAIL: checkout_tests.py 2: forced co fails if a dir obstructs a file
> FAIL: checkout_tests.py 3: forced co fails if a file obstructs a dir
> FAIL: checkout_tests.py 7: forced co with versioned obstruction
> FAIL: update_tests.py 13: bail when receive a file or dir named .svn
> FAIL: update_tests.py 25: obstructed update alters WC properties
> FAIL: update_tests.py 31: forced up fails with some types of obstructions
> FAIL: switch_tests.py 14: obstructed switch
> FAIL: switch_tests.py 21: forced switch fails with some types of
> obstuctions
> FAIL: blame_tests.py 2: annotate a binary file (*This is the one test
> that doesn't have the REPORT error, it fails instead because it allows svn
> blame of binary file without using --force).
> The log for the failures is attached.
Interesting. I have no idea what's causing these problems. What
version of Neon are you using for this? I'm on 0.25.4 here.
If someone on win32 could look into this, I'd appreciate it, because I
totally can't see the problem here, and I don't currently have a way
to run the tests on windows...
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 11 19:36:13 2006