Re: svn.collab.net intermittent failures

On Sat, 12 Apr 2003 kfogel@collab.net wrote:

> If there is anyone running a HEAD Subversion server with svnserve or
> Apache 2.0.45 right now, it would be great if you could run stress.pl
> and let us know how things go.

I ran 4 instances on a Dual Xeon 1.8Ghz system and all but one instances
of stress.pl completed normally. Here is the results for the one that
didn't complete normally:

Head revision: 233
Updating:
U wcstress.13473/trunk/foo1
G wcstress.13473/trunk/foo2
G wcstress.13473/trunk/bar1/foo1
U wcstress.13473/trunk/bar1/foo2
G wcstress.13473/trunk/bar2/foo1
Updated to revision 234.
Committing:
Sending wcstress.13473/trunk/bar1/foo1
Sending wcstress.13473/trunk/bar2/foo1
Sending wcstress.13473/trunk/bar2/foo2
Sending wcstress.13473/trunk/foo2
Transmitting file data .svn: Item already exists in filesystem
svn: Commit failed (details follow):
svn: successor id `0.0.t3' (for `0.0.sy') already exists in filesystem
'/home/dsummers/rpms/build/subversion-0.20.1/tools/dev/repostress/db'
svn: Berkeley DB deadlock error
svn: Berkeley DB error while reading node revision for filesystem
/home/dsummers/rpms/build/subversion-0.20.1/tools/dev/repostress/db:
DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock
unexpected commit fail: exit status: 256

I'm going to run them all again, I may have started up one of them
incorrectly and it doesn't take more than about 15 minutes or so to run.

Does this help any?

-- 
David Wayne Summers          "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org