After seeing grenade jobs fail the inner / outer timeout because it turns out there are > 5 minutes of time outside the main run job, I pulled together this new approach - https://review.openstack.org/#/c/75726/
Ideally it would be nice to not have to keep adding a
DEVSTACK_GATE_TIMEOUT into all the jobs, but instead use the existing
time definition from devstack-gate.yaml
wrappers:
- timeout:
timeout: 130
fail: true
What would be needed would be to make that timeout value available as an
environmental variable some how.
Any thoughts on how to make that happen?
-Sean
--
Sean Dague
Samsung Research America
[email protected] / [email protected]
http://dague.net
signature.asc
Description: OpenPGP digital signature
_______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
