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 DefaultCacheStatsHolderTests #14301

Open
opensearch-ci-bot opened this issue Jun 13, 2024 · 4 comments · Fixed by #14462
Open

[AUTOCUT] Gradle Check Flaky Test Report for DefaultCacheStatsHolderTests #14301

opensearch-ci-bot opened this issue Jun 13, 2024 · 4 comments · Fixed by #14462
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 13, 2024

Flaky Test Report for DefaultCacheStatsHolderTests

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

Details

Git Reference Merged Pull Request Build Details Test Name
24d7069 13994 40446 org.opensearch.common.cache.stats.DefaultCacheStatsHolderTests.testConcurrentRemoval
298aeda 13986 40014 org.opensearch.common.cache.stats.DefaultCacheStatsHolderTests.testConcurrentRemoval
97c2132 14054 40124 org.opensearch.common.cache.stats.DefaultCacheStatsHolderTests.testConcurrentRemoval
b79fedc 14254 40889 org.opensearch.common.cache.stats.DefaultCacheStatsHolderTests.testConcurrentRemoval
fe61816 14025 40279 org.opensearch.common.cache.stats.DefaultCacheStatsHolderTests.testConcurrentRemoval

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

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

@getsaurabh02
Copy link
Member

Untriaged as part of the Search Community Meeting. @kiranprakash154 volunteered to take a stab at this one.

@kiranprakash154 kiranprakash154 removed their assignment Jun 19, 2024
@kiranprakash154
Copy link
Contributor

@peteralfonsi will look into this
(cc: @getsaurabh02 )

@peteralfonsi
Copy link
Contributor

Like in #14300, I expect we will still see failures from PRs which don't have the fix merged in yet for at least a couple days. We can probably leave this open for a week or so, and make sure all new failures come from branches without the fix.

@peteralfonsi peteralfonsi self-assigned this Jun 26, 2024
@dblock dblock removed the untriaged label Jul 1, 2024
@dblock
Copy link
Member

dblock commented Jul 1, 2024

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

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: 🏗 In progress
Development

Successfully merging a pull request may close this issue.

7 participants