DB_INCOMPLETE solved, small new problem appearing though

I'm happy to report that Sander Striker's patch did the trick.

Though my `mass-commit' script is still running (just got past commit
#150), it's gotten no errors so far. While it's been doing commits
over ra_dav, I've been running `svnlook' repeatedly on the repository,
*and* doing simultaneous checkouts from the same repository. And
occasionally cleaning out old log files using `db_archive'. :-)

The mass-commit script never even pauses for breath. No errors from
the script, no errors in /var/log/httpd/error_log, and `svnlook'
reports a consistent repository every time. As best I can determine
from watching all of /proc/*/fd/, no one is holding open file
descriptors longer than necessary. Apache process sizes all look
reasonable too.

Oh wait, now it's on commit #284, and *still* no errors.

I have noticed that the update driver can get confused during those
simultaneous checkouts (i.e., a checkout going on during mass-commit)
and error out in get_editor.c:847 ("object of same name already
exists"). This will need looking into. Have done some detective work
already, and have a hypothesis about the cause -- Greg Stein or Ben,
if you take a look at issue #468, I think there's a chance you'll know
right away what's going on.

Ahh, mass-commit just finished commit #1000 with no errors.

So the summary of this mail is: mostly win with a little bit lose. :-)

-K

---------------------------------------------------------------------
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:37 2006