-
Notifications
You must be signed in to change notification settings - Fork 494
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
PartitionKeyRangeCacheTests are flaky #4732
Comments
@sourabh1007 can you please look into it? |
👀 |
If we can't prioritize this and identify a fix within this week, we should disable these tests until we can. It unduly impacts the productivity of the entire team. |
This is on a critical path of caches, lets look into it. |
If I am not wrong, it has nothing to do with client telemetry. It is just another test depending on |
## Description Removing dependency on `Task.Delay() ` ## Type of change - [] Bug fix (non-breaking change which fixes an issue) ## Closing issues To automatically close an issue: closes #4732
ClientTelemetryTestsBase has logic that is timing dependent. This causes the tests to be flaky.
Ideally, the
VerifyPkRangeCacheRefreshOnSplitWithErrorsAsync
method should be rewritten to correct these deficiencies.To Reproduce
This reproduces in the PR builds.
Expected behavior
Tests should not use calls to
Task.Delay
. The outcome of a test should be deterministic.The text was updated successfully, but these errors were encountered: