-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom exit code setting for threshold #1778
Comments
I still don't understand precisely why you want to do that, sorry. After all, the main purpose of the k6 thresholds is to act as a pass/fail criteria for the load test, so k6 returning with non-zero exit code is precisely meant to signal the CI system to treat the test run as a failure... In any case, wouldn't suppressing the exit code this way also work: k6 run whatever.js || true This way, even if k6 exits with a non-zero code, the script/CI job will not abort. |
Closing this issue due to lack of response. I though about it some more and there's a valid use case for wanting a |
Feature Description
When I run K6 in the docker, if threshold fails, it will cause exit code
99
(#870).I expect that it should be possible to customize the configuration, because my monitoring system will catch the exit, thinking this is an unexpected exit.
The text was updated successfully, but these errors were encountered: