Automatically deal with stuck buildds

Bug #330077 reported by Max Bowsher
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

https://launchpad.net/ubuntu/+source/ardour/1:2.7.1-2ubuntu1/+build/867461 started on kohnen at 2009-02-14 00:42:41 GMT, and was still going 2 days later, needing manual aborting.

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?

Celso Providelo (cprov)
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 :

Note that this implementation depends on proper 'abort' support on launchpad-buildd. See more information at bug #54730.

Changed in soyuz:
milestone: 2.2.5 → none
tags: added: buildfarm
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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