On 5/2/06, D.J. Heap <djheap@gmail.com> wrote:
> Are you using the native Win32 client or cygwin? AFAIK, the cygwin
> client doesn't include the workaround code. Which clients actually
> get the error and are they built using the native libraries or cygwin
> libraries or something else? Could there really be other processes
> holding onto the files (editors, etc.)?
We're using tortoise and intellij mainly - tortoise is native and
intellij uses javasvn (which I believe is independent of the svn
libs). I've also wondered about this being a source of error -
tortoise looking at a window in the background while intellij updates
it, for example. I can test this too.
I do use the cygwin client as well, but only from time to time. Theres
no correlation with the problem.
> The workaround code basically waits and retries for around 10 seconds
> per file -- that's quite a long time to wait for tag-alongs to finish
> whatever they were doing with each file.
Ah - that doesn't sound like what we're seeing, unless other work is
done in parallel with the wait. The commit/update where the bug occurs
is taking a normal amount of time, but this would be longer than 10s
anyway due to the size of the tree. I don't recall seeing 10s pauses
though.
> Also, you shouldn't have a broken tree afterwards. You should be able
> to retry the operation. If you are getting broken working copies,
> then please mail a good reproduction recipe to the dev list -- that's
> a bug.
Ok, I'll see if I can nail it down. We are getting (very) broken
working copies, but I presumed that since its in the faq its a known
issue. I'll set up a test repository and stress it a bit.
Cheers
Baz
PS sorry for the dupe. Must-hit-reply-to-all....doh.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 2 16:51:03 2006