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

[Search] Flaky test: Champion_OneShotUpload #43540

Closed
jsquire opened this issue Apr 19, 2024 · 1 comment
Closed

[Search] Flaky test: Champion_OneShotUpload #43540

jsquire opened this issue Apr 19, 2024 · 1 comment
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Search test-reliability Issue that causes tests to be unreliable
Milestone

Comments

@jsquire
Copy link
Member

jsquire commented Apr 19, 2024

The test Champion_OneShotUpload from sdk/search/Azure.Search.Documents/tests/Batching/BatchingTests.cs` has been consistent failing in the Azure.Core pipeline due to exceeding the global timeout. In order to stabilize, this test has been set to be ignored.

After the test has been fixed, it should be reenabled.

@jsquire jsquire added Storage Storage Service (Queues, Blobs, Files) Client This issue points to a problem in the data-plane of the library. test-reliability Issue that causes tests to be unreliable labels Apr 19, 2024
@jsquire jsquire added this to the Backlog milestone Apr 19, 2024
@jsquire jsquire added Search and removed Storage Storage Service (Queues, Blobs, Files) labels Apr 19, 2024
@jsquire jsquire changed the title [Storage] Flaky test: Champion_OneShotUpload [Search] Flaky test: Champion_OneShotUpload Apr 19, 2024
@jsquire
Copy link
Member Author

jsquire commented Apr 22, 2024

Closing in favor of #43552

@jsquire jsquire closed this as completed Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. Search test-reliability Issue that causes tests to be unreliable
Projects
Status: Done
Development

No branches or pull requests

2 participants