test(spanner): log warning instead of fail for stress test #2559
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Log a warning instead of failing the test if the TestStressSessionPool fails because one or more sessions are left on the server after closing the pool. This does occasionally happen; during local testing it happened once after running the test more than 10,000 times, but the reason is not clear. As the session would be garbage collected by the backend if this would happen in a real life scenario, it has been decided to leave this as is for now. Fixes #1981
googlebot
added
the
cla: yes
skuruppu
approved these changes
Jul 7, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Log a warning instead of failing the test if the TestStressSessionPool fails because one or more sessions are left on the server after closing the pool. This does occasionally happen; during local testing it happened once after running the test more than 10,000 times, but the reason is not clear. As the session would be garbage collected by the backend if this would happen in a real life scenario, it has been decided to leave this as is for now.
Fixes #1981