-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[BUG] org.opensearch.repositories.azure.AzureBlobStoreRepositoryTests.testContainerCreationAndDeletion / org.opensearch.repositories.azure.AzureBlobStoreRepositoryTests.testReadRange are flaky #10940
Labels
bug
Something isn't working
flaky-test
Random test failure that succeeds on second run
Storage:Snapshots
Comments
saratvemulapalli
added
the
flaky-test
Random test failure that succeeds on second run
label
Oct 26, 2023
8 tasks
reta
changed the title
[BUG] org.opensearch.repositories.azure.AzureBlobStoreRepositoryTests.testContainerCreationAndDeletion is flaky
[BUG] org.opensearch.repositories.azure.AzureBlobStoreRepositoryTests.testContainerCreationAndDeletion / org.opensearch.repositories.azure.AzureBlobStoreRepositoryTests.testReadRange are flaky
Nov 22, 2023
@shourya035 , can you please take this up ? |
Come across a similar test failure |
8 tasks
6 tasks
Closing in favour of #14291 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
flaky-test
Random test failure that succeeds on second run
Storage:Snapshots
Describe the bug
org.opensearch.repositories.azure.AzureBlobStoreRepositoryTests.testContainerCreationAndDeletion
is flaky.Below is the exception thrown -
To Reproduce
https://build.ci.opensearch.org/job/gradle-check/29044/testReport/junit/org.opensearch.repositories.azure/AzureBlobStoreRepositoryTests/testContainerCreationAndDeletion/
https://build.ci.opensearch.org/job/gradle-check/30312/testReport/junit/org.opensearch.repositories.azure/AzureBlobStoreRepositoryTests/testReadRange/
Expected behavior
The test must always pass.
The text was updated successfully, but these errors were encountered: