Builds get backed up too easily when a livefs builder fails

Bug #1163040 reported by Colin Watson on 2013-04-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu CD Images

Bug Description

If a live filesystem builder fails, then cdimage has a habit of ending up with a massive queue of builds waiting for it and stalling output for all other architectures. We should behave more gracefully in these circumstances. I have the following thoughts so far:

 * Keep a cdimage-side lock file for each builder machine so that there aren't so many triggers active, since this can make cleanup difficult
 * Apply a configurable upper bound to the run-time of any given builder, and locally mark it failed after that (this depends on the previous item, since otherwise we can't tell the difference between "running" and "waiting for lock")

Adam Conrad (adconrad) wrote :

This doesn't seem particularly relevant in the new world order of farming livefs builds off to launchpad, though technically the code is still there to handle legacy builders. Do we care, though?

Changed in ubuntu-cdimage:
status: Triaged → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers