CI jobs timeout at 97 minutes instead of 153
Bug #1593740 reported by
Emilien Macchi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
Critical
|
Paul Belanger | ||
Bug Description
Currently investigating why ALL TripleO jobs are failing.
Example of failure: http://
We think it's related to Infa move from Jenkins to Zuul runner
Revision history for this message
| Emilien Macchi (emilienm) wrote | #1 |
| Changed in tripleo: | |
| status: | New → Confirmed |
| importance: | Undecided → Critical |
| tags: | added: alert |
| summary: |
- TripleO CI is failing with zuul-launcher + CI jobs timeout at 97 minutes instead of 153 |
| Changed in tripleo: | |
| assignee: | nobody → Emilien Macchi (emilienm) |
Revision history for this message
| Emilien Macchi (emilienm) wrote | #2 |
| Changed in tripleo: | |
| assignee: | Emilien Macchi (emilienm) → Paul Belanger (pabelanger) |
Revision history for this message
| Emilien Macchi (emilienm) wrote | #3 |
| Changed in tripleo: | |
| status: | Confirmed → Fix Released |
| tags: | removed: alert |
To post a comment you must log in.
Before we had:
Job timeout set to: 153 minutes with jenkins
and now:
Job timeout set to: 97 minutes with Zuul
Looking at http://
Something in Zuul is not exporting BUILD_TIMEOUT, we're investigating.