[CLIENT-4040] Fix flaky test case "test_neg_exists_with_low_timeout" in test_exists.py #917
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This test case passes a low total_timeout to
client.put()which still passes in most environments that have a low e2e latency. But if the e2e latency is high enough, thisclient.put()would fail and the test will be unable to get the record metadata using client.exists(). We increase the total_timeout so thatclient.put()still succeeds with a relatively low total timeout.TODO