Skip to content

Conversation

@dnhatn
Copy link
Member

@dnhatn dnhatn commented Oct 2, 2025

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.

@dnhatn dnhatn added v9.2.0 v8.19.1 >test Issues or PRs that are addressing/adding tests :Analytics/ES|QL AKA ESQL v9.1.6 v9.2.1 auto-backport Automatically create backport pull requests when merged and removed v9.2.0 labels Oct 2, 2025
@dnhatn dnhatn requested a review from nik9000 October 2, 2025 17:06
@dnhatn dnhatn marked this pull request as ready for review October 2, 2025 17:06
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-analytical-engine (Team:Analytics)

@elasticsearchmachine elasticsearchmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Oct 2, 2025
Copy link
Member

@nik9000 nik9000 left a 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.

@nik9000
Copy link
Member

nik9000 commented Oct 3, 2025

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.

Copy link
Contributor

@ivancea ivancea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

Copy link
Contributor

@craigtaverner craigtaverner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice.

@dnhatn
Copy link
Member Author

dnhatn commented Oct 4, 2025

Thanks friends!

@dnhatn dnhatn merged commit c0bb172 into elastic:main Oct 4, 2025
34 checks passed
@dnhatn dnhatn deleted the ensure-cluster-running branch October 4, 2025 00:58
dnhatn added a commit to dnhatn/elasticsearch that referenced this pull request Oct 4, 2025
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.
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.19 Commit could not be cherrypicked due to conflicts
9.1 Commit could not be cherrypicked due to conflicts
9.2

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 135862

elasticsearchmachine pushed a commit that referenced this pull request Oct 4, 2025
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Analytics/ES|QL AKA ESQL auto-backport Automatically create backport pull requests when merged backport pending Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) >test Issues or PRs that are addressing/adding tests v8.19.1 v9.1.6 v9.2.1 v9.3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants