buildd master explodes if a slave goes bad mid-build

Bug #32154 reported by Daniel Silverstone
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Celso Providelo

Bug Description

If a slave is marked NOT OK mid-build then the buildd master gets very confused and starts throwing exceptions all over the place.

We should clear the builder column of any buildqueue item which is assigned to a builder when we decide to mark it bad.

Revision history for this message
Celso Providelo (cprov) wrote :

Makes sense and it's not difficult to implement

Changed in launchpad-buildd:
assignee: nobody → cprov
status: Unconfirmed → Confirmed
Revision history for this message
Daniel Silverstone (dsilvers) wrote :

Done?

Revision history for this message
Celso Providelo (cprov) wrote :

Not yet, but it's not *high* priority.

Changed in soyuz:
assignee: cprov → nobody
importance: High → Medium
Revision history for this message
Celso Providelo (cprov) wrote :

It seems to be already fixed, but it will be revised during bug #343683 fix.

Changed in soyuz:
assignee: nobody → cprov
milestone: none → pending
Revision history for this message
Celso Providelo (cprov) wrote :

I can confirm it's fixed after r8300.

Changed in soyuz:
milestone: pending → 2.2.4
status: Triaged → Fix Committed
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.