Re: Tests

"D.J. Heap" <djheap@dhiprovo.com> writes:

> I've been experiencing a commit test failure occasionally and was
> wondering if anyone else was seeing it. What's odd is that it doesn't
> fail all the time even running against the same binaries. I can also go
> through the steps manually and everything appears to work as far as I
> can tell, so I haven't been too concerned.

That appears to indicate some sort of race. Do the two failures
always occur together? On Unix it is possible to run a single test
using

   % <source_dir>/subversion/tests/clients/cmdline/commit_tests.py 21

(add -v for verbose output) can you do the same on Windows? If you
run the test repeatedly how often does it fail?

There was a testsuite race in past (copying a repository while
svnserve was still accessing it), but I see you are running over
ra_local and commit test 21 is simple: add a file, commit, update,
commit. There is not much scope for a testsuite race there. Could this
be another symptom of the Windows filesystem race? What do the
working copy and repository look like after the test fails?

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org