hard timeouts not built in
Bug #1629345 reported by
Aaron Bentley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-ci-tools |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
We can't determine hard timeouts from soft timeouts (or vice-versa), because hard timeouts are implemented using /usr/bin/timeout, and are not part of our python scripts. But juju-ci-tools has its own timeout implementation. Scripts executed with --hard-timeout could re-execute themselves via timeout.py.
Or, scripts could vary their timeout based on what cloud they're being used with.
| Changed in juju-ci-tools: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
