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 SearchingIT #15844

Open
opensearch-ci-bot opened this issue Sep 6, 2024 · 1 comment
Open

[AUTOCUT] Gradle Check Flaky Test Report for SearchingIT #15844

opensearch-ci-bot opened this issue Sep 6, 2024 · 1 comment
Labels
autocut flaky-test Random test failure that succeeds on second run >test-failure Test failure from CI, local build, etc.

Comments

@opensearch-ci-bot
Copy link
Collaborator

opensearch-ci-bot commented Sep 6, 2024

Flaky Test Report for SearchingIT

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

Details

Git Reference Merged Pull Request Build Details Test Name
6a29119 16049 48351 org.opensearch.backwards.SearchingIT.testMultiGet
7b0846e 15657 46977 org.opensearch.backwards.SearchingIT.testMultiGet
848e5c6 16057 48343 org.opensearch.backwards.SearchingIT.testMultiGet

The other pull requests, besides those involved in post-merge actions, that contain failing tests with the SearchingIT 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 6, 2024
@reta reta removed the untriaged label Sep 30, 2024
@reta
Copy link
Collaborator

reta commented Sep 30, 2024

[Catch All Triage - 1, 2, 3, 4]

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.
Projects
None yet
Development

No branches or pull requests

2 participants