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 sean at dague.net / sean.dague at samsung.com http://dague.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 482 bytes Desc: OpenPGP digital signature URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20140223/2c005064/attachment.pgp>