You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 4, 2024. It is now read-only.
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: