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 ICacheKeySerializerTests #14504

Closed
opensearch-ci-bot opened this issue Jun 22, 2024 · 2 comments · Fixed by #14564
Closed

[AUTOCUT] Gradle Check Flaky Test Report for ICacheKeySerializerTests #14504

opensearch-ci-bot opened this issue Jun 22, 2024 · 2 comments · Fixed by #14564
Assignees
Labels
autocut flaky-test Random test failure that succeeds on second run Search:Performance >test-failure Test failure from CI, local build, etc.

Comments

@opensearch-ci-bot
Copy link
Collaborator

opensearch-ci-bot commented Jun 22, 2024

Flaky Test Report for ICacheKeySerializerTests

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

Details

Git Reference Merged Pull Request Build Details Test Name
4a92ccc 14501 41510 org.opensearch.common.cache.serializer.ICacheKeySerializerTests.testInvalidInput

The other pull requests, besides those involved in post-merge actions, that contain failing tests with the ICacheKeySerializerTests 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 Jun 22, 2024
@peteralfonsi
Copy link
Contributor

Will take a look at this one

@peternied
Copy link
Member

[Triage - attendees 1 2 3]
Approving this autocut issue

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 Search:Performance >test-failure Test failure from CI, local build, etc.
Projects
Status: Done
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

4 participants