We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Encountered flaky tests in BlobStoreRepositoryTests. Below are the flaky tests -
To Reproduce Check console output in https://build.ci.opensearch.org/job/gradle-check/20753
Expected behavior Tests should pass.
Plugins Please list all plugins currently enabled.
Screenshots If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Reproducible on main with -
./gradlew ':server:test' --tests "org.opensearch.repositories.blobstore.BlobStoreRepositoryTests.testRetrieveShallowCopySnapshotCase1" -Dtests.seed=F6DEB85546834F2C -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=no-NO -Dtests.timezone=Antarctica/Rothera -Druntime.java=20
Sorry, something went wrong.
Looks like this flakyness is introduced with #8719
We mandated use of translog enabled remote indices, earlier these tests were just using segment store enabled remote indices
Successfully merging a pull request may close this issue.
Describe the bug
Encountered flaky tests in BlobStoreRepositoryTests. Below are the flaky tests -
To Reproduce
Check console output in https://build.ci.opensearch.org/job/gradle-check/20753
Expected behavior
Tests should pass.
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: