Skip to content

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

Merged
merged 6 commits into from
Oct 16, 2023

Conversation

mafredri
Copy link
Member

We also end all failed phases and add the error tag in Grafana.

We also end all failed phases and add the `error` tag in Grafana.
@mafredri mafredri self-assigned this Oct 16, 2023
@mafredri mafredri requested a review from johnstcn October 16, 2023 14:04
Comment on lines +66 to +74
# Debug scenarios, for testing the runner.
"debug:success")
maybedryrun "$DRY_RUN" sleep 10
status=0
;;
"debug:error")
maybedryrun "$DRY_RUN" sleep 10
status=1
;;
Copy link
Member

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
Copy link
Member

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

Copy link
Member Author

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}. 😜)

@mafredri mafredri merged commit 43f26df into main Oct 16, 2023
@mafredri mafredri deleted the mafredri/feat-scaletest-run-all-scenarios-log-failures branch October 16, 2023 15:18
@github-actions github-actions bot locked and limited conversation to collaborators Oct 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants