jobs that never start eventually give zuul indigestion
Bug #1281320 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Zuul |
New
|
Undecided
|
Unassigned | ||
Bug Description
If a job doesn't start for any particular reason, zuul keeps it forever and doesn't time it out. Over time, if the cause is (e.g,) a necessary provider being offline, this leads to very many stuck jobs, which is bad for performance and for usability.
Revision history for this message
| James E. Blair (corvus) wrote | #1 |
| Changed in openstack-ci: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: zuul |
| no longer affects: | openstack-ci |
To post a comment you must log in.
We should have a timeout, configurable in the "job:" section of the layout.conf. The build should be marked "LOST" or perhaps something like "NODE_TIMEOUT" if it exceeded. It should default to no timeout (wait forever).