should track and then disable failing jobs
Bug #693241 reported by
Martin Pool
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
In the context of <https:/
Launchpad should notice when a job repeatedly fails, and eventually disable it, and log what's happening.
There may already be code for this in soyuz or branch imports? It should be put into a standard place.
Detecting failed jobs should include detecting when the process running them simply disappeared because of eg hitting a resource limit or crashing without a Python exception.
tags: | added: jobs |
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
On Wednesday 22 December 2010 01:43:48 you wrote:>
> There may already be code for this in soyuz or branch imports? It
> should be put into a standard place.
The buildd-manager has rudimentary detection by counting failures and trying
to work out whether the job or the builder (job runner in effect) is failing
more.
We could generalise this into a mixin implementing IHasFailures or similar.