Automatically deal with stuck buildds
Bug #330077 reported by
Max Bowsher
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
https:/
Celso asked me on IRC to file a bug suggesting some sort of automated handling of stuck builds based on build-time estimates - i.e. reset if the build has no activity and is past a certain percentage leeway over the estimated time.
For reference, the live console output webpage was showing "Session terminated, killing shell... ...killed." at the end, for the specific stuck build I'm mentioning, suggesting that perhaps the buildd infrastructure had already tried to terminate the build but got stuck doing so?
| Changed in soyuz: | |
| importance: | Undecided → Wishlist |
| milestone: | none → 2.2.5 |
| status: | New → Triaged |
| Changed in soyuz: | |
| importance: | Wishlist → Low |
Revision history for this message
| Celso Providelo (cprov) wrote | #1 |
| Changed in soyuz: | |
| milestone: | 2.2.5 → none |
| tags: | added: buildfarm |
To post a comment you must log in.
Note that this implementation depends on proper 'abort' support on launchpad-buildd. See more information at bug #54730.