-
Notifications
You must be signed in to change notification settings - Fork 903
feat(scaletest/templates): run all scenarios even on failure #10290
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
feat(scaletest/templates): run all scenarios even on failure #10290
Conversation
We also end all failed phases and add the `error` tag in Grafana.
# Debug scenarios, for testing the runner. | ||
"debug:success") | ||
maybedryrun "$DRY_RUN" sleep 10 | ||
status=0 | ||
;; | ||
"debug:error") | ||
maybedryrun "$DRY_RUN" sleep 10 | ||
status=1 | ||
;; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_
_ __ (_) ___ ___
| '_ \| |/ __/ _ \
| | | | | (_| __/
|_| |_|_|\___\___|
|
||
wait_baseline "${SCALETEST_PARAM_LOAD_SCENARIO_BASELINE_DURATION}" | ||
done | ||
|
||
if ((${#failed} > 0)); then | ||
log "Load scenarios failed: ${!failed[*]}" | ||
for scenario in "${!failed[@]}"; do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't know you could do this :o
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, it's the syntax for accessing associative array keys. 💪🏻 (I much prefer the Zsh way though for scenario in ${(k)failed}
or even for scenario code in ${(kv)failed}
. 😜)
We also end all failed phases and add the
error
tag in Grafana.