Lost builders don't have their jobs unassigned on rescue
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
William Grant |
Bug Description
If a launchpad-buildd slave's idea of its current job doesn't match the master's, it is declared to be lost and BuilderInteract
This bug currently resolves in lost builders occasionally getting failed when they eventually transition to WAITING/ABORTED, because the status gets inappropriately passed down to a job that is in the wrong state. Affected builders can be recovered by simply reenabling them, as the cleanup has already taken place.
Related branches
- Steve Kowalik (community): Approve (code)
-
Diff: 614 lines (+211/-191)4 files modifiedlib/lp/buildmaster/interactor.py (+35/-54)
lib/lp/buildmaster/manager.py (+46/-64)
lib/lp/buildmaster/tests/test_interactor.py (+47/-62)
lib/lp/buildmaster/tests/test_manager.py (+83/-11)
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
Fixed in stable r16760 <http:// bazaar. launchpad. net/~launchpad- pqm/launchpad/ stable/ revision/ 16760>.