Translations-to-branch exporter reports locked branch, but not which
Bug #884599 reported by
Jeroen T. Vermeulen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Critical
|
Jeroen T. Vermeulen | ||
Bug Description
The translations export-to-branch script has been reporting the same failure for days now: a single locked branch.
ERROR Failure: LockContention(
This probably means that one particular branch is in an incorrect locked state, e.g. as a result of bug 513669. But the error doesn't say which branch this is, making it hard to do anything about it.
Note that this bug is not about the broken lock, or about how to deal with it. A single manual email to the branch owner could be enough to make the error go away for a long time. But the error message should identify where the failure happens.
Related branches
lp:~jtv/launchpad/bug-884599
- Abel Deuring (community): Approve (code)
-
Diff: 89 lines (+16/-10)4 files modifiedlib/lp/registry/interfaces/productseries.py (+3/-3)
lib/lp/translations/doc/translations-export-to-branch.txt (+4/-2)
lib/lp/translations/scripts/tests/test_translations_to_branch.py (+2/-2)
lib/lp/translations/scripts/translations_to_branch.py (+7/-3)
| Changed in launchpad: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Jeroen T. Vermeulen (jtv) |
| tags: | added: trivial |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #1 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
Revision history for this message
| Jeroen T. Vermeulen (jtv) wrote | #2 |
| tags: |
added: qa-needstesting removed: qa-ok |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in stable r14441 <http://