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
I think we can fix this easily by making the timeout default dynamic. If --bench is not specified, the 5s timeout is fine (that's more than enough time a query to return). If --bench is specified, we can just crank the timeout to 30s as that would give the Go benchmark runner enough time to find a stable measurement.
Expected Behavior
opa test --bench testing.rego
to report the result of benchmarking a simple policy.Actual Behavior
Steps to Reproduce the Problem
testing.rego
$ opa test --bench testing.rego
Additional Info
Setting the
--timeout
flag to 30s provides the benchmark result. Two things stand out to me here:--timeout
is provided, I believe the default should be to run until finished.--timeout
is provided and exceeded, a human readable message should be printed.The text was updated successfully, but these errors were encountered: