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

[AUTOCUT] Gradle Check Flaky Test Report for ChildQuerySearchIT #15907

Open
opensearch-ci-bot opened this issue Sep 12, 2024 · 0 comments
Open
Labels
autocut flaky-test Random test failure that succeeds on second run >test-failure Test failure from CI, local build, etc. untriaged

Comments

@opensearch-ci-bot
Copy link
Collaborator

opensearch-ci-bot commented Sep 12, 2024

Flaky Test Report for ChildQuerySearchIT

Noticed the ChildQuerySearchIT has some flaky, failing tests that failed during post-merge actions.

Details

Git Reference Merged Pull Request Build Details Test Name
1a1b79d 15043 43729 org.opensearch.join.query.ChildQuerySearchIT.classMethod

org.opensearch.join.query.ChildQuerySearchIT.testScoreForParentChildQueriesWithFunctionScore {p0={"search.concurrent_segment_search.enabled":"true"}}
58794ad 15651 47726 org.opensearch.join.query.ChildQuerySearchIT.classMethod

org.opensearch.join.query.ChildQuerySearchIT.testParentChildQueriesViaScrollApi {p0={"search.concurrent_segment_search.enabled":"true"}}

The other pull requests, besides those involved in post-merge actions, that contain failing tests with the ChildQuerySearchIT class are:

For more details on the failed tests refer to OpenSearch Gradle Check Metrics dashboard.

@opensearch-ci-bot opensearch-ci-bot added >test-failure Test failure from CI, local build, etc. autocut flaky-test Random test failure that succeeds on second run untriaged labels Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autocut flaky-test Random test failure that succeeds on second run >test-failure Test failure from CI, local build, etc. untriaged
Projects
None yet
Development

No branches or pull requests

1 participant