-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Skip spec tests when test cluster broken #135862
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
Conversation
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
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.
Seems like a good idea. We should tell everyone this is happening.
|
Previously you have to look at the first failure. But after this you'll look at the only failure. It'll just be that everything else is skipped. This'll kick in if the cluster crashes or if it unassignes a bunch of shards, likely because a node crashes. All things that can happen in testing. |
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.
![]()
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.
Nice.
|
Thanks friends! |
If the test clusters are broken, we should stop running spec tests; otherwise we will see a lot of failures, making triage and investigating more difficult.
💔 Backport failed
You can use sqren/backport to manually backport by running |
If the test clusters are broken, we should stop running spec tests; otherwise we will see a lot of failures, making triage and investigating more difficult.