eg wrote:
> If I understand you correctly, the same tests were also
able to run on
> 1.3.1 after a few tries. "If" there is a
"potential deadlock" issue,
> it may or may not occur every time the test is run,
depending on the
> nature of the problem, initial conditions, what else is
running..
Of course.
> If someone is interested in trying to track it down (or
see if they
> can), it may require running tests over a longer period
of time on
> multiple cpu machines perhaps with vary load. I don't
have a multi-cpu
> or dual-core box at this time, so I can't assist.
Well, it usually boils down to a tedious code review...
I ran tests with the mainline code and bdb-4.4 for several
hours, with
both multi-process and multi-threaded access to the
repository. I saw no
deadlocks.
Certainly that's not proof that there aren't any, but
it's good enough
for me.
-- Brane
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe subversion.tigris.org
For additional commands, e-mail: dev-helpsubversion.tigris.org
|