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 MetadataCreateIndexServiceTests #17291

Closed
opensearch-ci-bot opened this issue Feb 7, 2025 · 6 comments · Fixed by #17384
Closed
Assignees
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 Feb 7, 2025

Flaky Test Report for MetadataCreateIndexServiceTests

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

Details

Git Reference Merged Pull Request Build Details Test Name
1673e74 17288 53215 org.opensearch.cluster.metadata.MetadataCreateIndexServiceTests.testCreateIndexWithContextDisabled
3f793b6 17252 53188 org.opensearch.cluster.metadata.MetadataCreateIndexServiceTests.testCreateIndexWithContextDisabled

The other pull requests, besides those involved in post-merge actions, that contain failing tests with the MetadataCreateIndexServiceTests 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 Feb 7, 2025
@rishabhmaurya
Copy link
Contributor

Another failure - https://build.ci.opensearch.org/job/gradle-check/53286/

seed:

./gradlew ':server:test' --tests "org.opensearch.cluster.metadata.MetadataCreateIndexServiceTests.testCreateIndexWithContextDisabled" -Dtests.seed=86A37BB82FED4A6E -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=bho-Deva-IN -Dtests.timezone=America/Asuncion -Druntime.java=23

Unable to reproduce though locally.

@mgodwan since you added this test, do you mind taking a look. Thank you

@mgodwan
Copy link
Member

mgodwan commented Feb 11, 2025

This seems to be a side effect of tests running together, where some test is enabling the FF, and the current test relies on FF being disabled.
Will raise a PR to fix this.

@kkewwei
Copy link
Contributor

kkewwei commented Feb 20, 2025

It happens again in #17392(https://build.ci.opensearch.org/job/gradle-check/53681/) with the newest main branch.

@prudhvigodithi
Copy link
Member

I can see the failure of testCreateIndexWithContextDisabled https://build.ci.opensearch.org/job/gradle-check/53741/testReport/org.opensearch.cluster.metadata/MetadataCreateIndexServiceTests/testCreateIndexWithContextDisabled/ on my draft PR #17299, @kkewwei can you please check if the test is still flaky ?
Thanks
@getsaurabh02

@prudhvigodithi
Copy link
Member

Let me try with re-basing the changes from main.

@kkewwei
Copy link
Contributor

kkewwei commented Feb 21, 2025

@cwperks @prudhvigodithi , It' ok now, I'm very sorry for the confusion I caused you.

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
6 participants