Skip to content
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

Disable KqlQueryBuilderTests on non-snapshots build. #117025

Merged
merged 5 commits into from
Nov 20, 2024

Conversation

afoucret
Copy link
Contributor

Fix for #116487

@afoucret afoucret added >test-failure Triaged test failures from CI auto-backport Automatically create backport pull requests when merged :SearchOrg/Relevance Label for the Search (solution/org) Relevance team Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch v8.17.0 labels Nov 19, 2024
@afoucret afoucret requested review from carlosdelest, ioanatia and a team November 19, 2024 14:03
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/search-eng (Team:SearchOrg)

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/search-relevance (Team:Search - Relevance)

Comment on lines 29 to 38
tasks.named('yamlRestTest').configure {
usesDefaultDistribution()

/****************************************************************
* Enable QA/rest integration tests for snapshot builds only *
* TODO: Enable for all builds upon this feature release *
****************************************************************/
enabled = buildParams.isSnapshotBuild()
}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is not necessary anymore, since it is controlled by a capability.

@@ -34,6 +36,10 @@
import static org.hamcrest.Matchers.nullValue;

public class KqlQueryBuilderTests extends AbstractQueryTestCase<KqlQueryBuilder> {
@Before
Copy link
Member

Choose a reason for hiding this comment

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

I think the following works as well, so it avoids skipping the individual tests?

Suggested change
@Before
@BeforeClass

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done!

@afoucret afoucret enabled auto-merge (squash) November 20, 2024 12:15
@afoucret afoucret merged commit 537bba6 into elastic:main Nov 20, 2024
15 of 16 checks passed
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.x Commit could not be cherrypicked due to conflicts

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

@afoucret
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
8.x

Questions ?

Please refer to the Backport tool documentation

afoucret added a commit to afoucret/elasticsearch that referenced this pull request Nov 20, 2024
(cherry picked from commit 537bba6)

# Conflicts:
#	muted-tests.yml
#	x-pack/plugin/kql/build.gradle
afoucret added a commit that referenced this pull request Nov 20, 2024
(cherry picked from commit 537bba6)

# Conflicts:
#	muted-tests.yml
#	x-pack/plugin/kql/build.gradle
rjernst pushed a commit to rjernst/elasticsearch that referenced this pull request Nov 20, 2024
alexey-ivanov-es pushed a commit to alexey-ivanov-es/elasticsearch that referenced this pull request Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Automatically create backport pull requests when merged backport pending :SearchOrg/Relevance Label for the Search (solution/org) Relevance team Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch >test-failure Triaged test failures from CI v8.17.0 v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants