Skip to content
This repository has been archived by the owner on Mar 4, 2024. It is now read-only.

support benchmark action timeout #28

Open
kwmonroe opened this issue May 6, 2016 · 1 comment
Open

support benchmark action timeout #28

kwmonroe opened this issue May 6, 2016 · 1 comment

Comments

@kwmonroe
Copy link
Contributor

kwmonroe commented May 6, 2016

We currently run the benchmark actions with timeout = -1 (no timeout). If we're hung, this will stall cwr forever. It would be nice if we could add a key to either the benchmark definition (to specify timeout per benchmark) or an overall testplan benchmark timeout (to specify a timeout for all benchmarks if/when multiple actions are supported in cwr).

@seman
Copy link
Contributor

seman commented May 9, 2016

Currently, the timeout is set to 1 hr and won't run forever. Changing this to enhancement for adding a timeout key in a test plan.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants