Please add a button to permanently fail a build

Bug #494560 reported by LaMont Jones
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Critical
Unassigned

Bug Description

Today we noticed that https://edge.launchpad.net/~neon/+archive/ppa/+build/1382484 was infinite looping with output, which means that the slave will never decide that the build is hung, until it's out of disk space, at which point lp-buildd will fail with some other error, causing soyuz to decide that the ppa went away, and launch it on another ppa buildd.

The only solution today is to manually supersede the build record, and then to reset the looping ppa. This is, of course, suboptimal.

Please add a button to /builders/$HOST (and/or the build record itself??) to do the following:
1) mark the build superseded
2) cause the build to terminate. (for now, that involves getting to the path where we ppa-reset or so, once lp-buildd understands how to abort the build properly, then we should switch to using that path.)

It probably makes sense to even allow the owner of the ppa to kill a looping build with fire, as above.

Changed in soyuz:
status: New → Triaged
tags: added: soyuz-build
Changed in soyuz:
importance: Undecided → High
Revision history for this message
Julian Edwards (julian-edwards) wrote :

See also bug 173018 which is possibly a dupe.

tags: added: buildfarm
Gavin Panella (allenap)
Changed in launchpad:
status: Triaged → In Progress
assignee: nobody → Gavin Panella (allenap)
Gavin Panella (allenap)
Changed in launchpad:
assignee: Gavin Panella (allenap) → nobody
Changed in launchpad:
status: In Progress → Triaged
Revision history for this message
Francis J. Lacoste (flacoste) wrote :

Escalated by Tom.

tags: added: canonical-losa-lp escalated
removed: lp-soyuz
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Bumping to critical, since it's marked escalated.

Changed in launchpad:
importance: High → Critical
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.