Re: ra_svn deadlock

Philip Martin <philip@codematters.co.uk> writes:

> > Since svnserve is holding a repository open for the lifetime of a
> > connection, then depending on how locking works, it may be impossible
> > for two client connections to access the same repository at the same
> > time. That would also affect diff-tests 5.
>
> We often have multiple "clients" holding database locks at the same
> time, I don't think that's a problem. diff-tests 5 passes :)
>
> > I don't know why I haven't run into this in my tests. Maybe a db 4.0.14
> > vs. db 4.1 issue.
>
> I'm using 4.1.

Oops, sent that before it was finished.

I'm using 4.1, and with the svnadmin recover hack all the tests pass.
In fact, they pass if I simply do a time.sleep(2) before copying the
repository, and then I don't need to run recover. So I conclude that
the cause of the problem is that the svnserve processs terminates
asychronously, and causes the repository to get modified during the
copy. That's not an svnserve bug, rather externals_tests.py is not
doing the right thing when copying a repository.

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