LockContention failures
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Distributed Development |
Confirmed
|
High
|
Unassigned |
Bug Description
When package-importer gets a LockContention while trying to push up an import, it should reset its state and retry later.
The idea is that if you are getting write lock contention, that means someone is probably uploading the update that you think you are going to be pushing, and we would rather just use their upload.
Currently this exact traceback is set as a retry-the-import condition. It should be more explicitly done inside the code.
Unable to obtain lock held by <email address hidden>
at crowberry [process #31466], acquired 0 seconds ago.
See "bzr help break-lock" for more.
Traceback (most recent call last):
File "/srv/package-
local_
File "/srv/package-
push_
File "/srv/package-
overwrite=
File "/srv/package-
dir_
File "/usr/lib/
overwrite, stop_revision=
File "/usr/lib/
*args, **kwargs)
File "/usr/lib/
_override_
File "/usr/lib/
target.
File "/usr/lib/
remote_tokens = self._remote_
File "/usr/lib/
repo_token or '', **err_context)
File "/usr/lib/
return self._client.
File "/usr/lib/
result, protocol = self.call_
File "/usr/lib/
method, args, expect_
File "/usr/lib/
expect_
File "/usr/lib/
_translate_
File "/usr/lib/
raise errors.
bzrlib.
Changed in udd: | |
assignee: | nobody → canonical-bazaar (canonical-bazaar) |
importance: | Low → High |
Changed in udd: | |
assignee: | canonical-bazaar (canonical-bazaar) → nobody |