Karl Fogel <kfogel@newton.ch.collab.net> writes:
> Philip Martin <pmartin@uklinux.net> writes:
> > The deadlock I reported in
> >
> > http://subversion.tigris.org/servlets/ReadMsg?msgId=42676&listName=dev
> >
> > where two separate working copies commit to the same repository, seems
> > to be easy to reproduce at present. I am building against db-4.0.14 as
> > an experiment, and the script in the mail above now provokes deadlock
> > fairly often. I don't think 4.0.14 is itself the cause of the deadlock
> > as I could sometimes provoke it when using 3.3.11 (but I may be wrong
> > here :-)
>
> Hmmm. Philip, is what you are seeing related to
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=557
>
> and
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=558
>
It's the same test that caused those issues to be raised. However, 557
is marked fixed and 558 only mentions an update bug. I am seeing
deadlock between two commits, which I didn't expect to be covered by
either issue.
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:51 2006