-
Notifications
You must be signed in to change notification settings - Fork 8.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
Add 2 flaky retries to ES snapshot jobs #64553
Add 2 flaky retries to ES snapshot jobs #64553
Conversation
Pinging @elastic/kibana-operations (Team:Operations) |
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.
LGTM
@elasticmachine merge upstream |
@elasticmachine merge upstream |
Skipped a flaky test and notified the APM folks about the other one, it hasn't failed on a tracked branch yet but this is the third failure across three different PRs in the last three days... |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
# Conflicts: # .ci/es-snapshots/Jenkinsfile_verify_es # vars/prChanges.groovy
The ES snapshot verification jobs currently don't do retries at all for flaky failures... This enables retries with an allowance of two failures (two separate ciGroups can each fail once, a ciGroup that fails twice is still a full failure).
Also, adding this directory to the CI skips because it is currently pointless to run PR CI for it. It will still run on this PR because I changed
vars/
.