The buildd-manager shares failure modes for connection failures and reset failures
Bug #586362 reported by
Julian Edwards
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Julian Edwards | ||
Bug Description
ResetDispatchResult is used for both failures to reset and dispatch failures, the latter which is more common and caused by transient communication failures.
This means we can't implement marking a builder as failed for reset failures until there's a separate handler for dispatch failures.
See also bug 369109
Related branches
lp:~julian-edwards/launchpad/buildd-failure-counting
- Jonathan Lange (community): Approve
- Stuart Bishop (community): Approve (db)
- Robert Collins: Pending (db) requested
- Diff: 0 lines
| Changed in soyuz: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: buildd-manager |
| Changed in soyuz: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Julian Edwards (julian-edwards) |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote Bug fixed by a commit | #1 |
| Changed in soyuz: | |
| milestone: | none → 10.09 |
| tags: | added: qa-needstesting |
| Changed in soyuz: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-untestable removed: qa-needstesting |
| Changed in soyuz: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in db-stable r9702 <http://