=?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@xbc.nu> writes:
> Branko Čibej wrote:
>
> >I now have stress.pl running on Windows
> >
> ...
>
> >Looks fine for now, so I'll let it run overnight.
> >
> >
>
> Oops.
>
> Updating:
> U wcstress.3768\trunk\foo1
> U wcstress.3768\trunk\foo2
> G wcstress.3768\trunk\bar1\foo1
> G wcstress.3768\trunk\bar1\foo2
> G wcstress.3768\trunk\bar2\foo1
> G wcstress.3768\trunk\bar2\foo2
> Updated to revision 369.
> Committing:
> Status:
> svn: Item already exists in filesystem
> svn: successor id `0.0.v4' (for `0.0.uv') already exists in filesystem 'r://repostress/db'
> svn: Berkeley DB deadlock error
> svn: Berkeley DB error while reading node revision for filesystem r://repostress/db:
> DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock
> svn st -u wcstress.3768: failed: 256
So, I'm remember how we print error messages, it looks like the
deadlock happens first, and *then* the "already exists" is tacked onto
it.
err = svn_fs__bdb_get_node_revision (NULL, fs, new_id, trail);
if ((! err) || (err->apr_err != SVN_ERR_FS_ID_NOT_FOUND))
{
svn_string_t *id_str = svn_fs_unparse_id (id, trail->pool);
svn_string_t *new_id_str = svn_fs_unparse_id (new_id, trail->pool);
return svn_error_createf
(SVN_ERR_FS_ALREADY_EXISTS, err,
"successor id `%s' (for `%s') already exists in filesystem '%s'",
new_id_str->data, id_str->data, fs->path);
}
Ah. So, our error message isn't really all that helpful, since any
error except "not found" (include "deadlock error") will make it
appear that there is, to use TuttSpeak :-), a NodeRev PK conflict. I
remain confident that our filesystem code isn't generating clashing
node-rev-ids.
Still, the deadlock concerns me.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 20 06:46:04 2003