bigquerystorage: excise retry expectations in tests for DEADLINE_EXCEEDED#5219
Merged
sduskis merged 2 commits intogoogleapis:masterfrom May 24, 2019
Merged
bigquerystorage: excise retry expectations in tests for DEADLINE_EXCEEDED#5219sduskis merged 2 commits intogoogleapis:masterfrom
sduskis merged 2 commits intogoogleapis:masterfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5219 +/- ##
=========================================
Coverage 50.42% 50.42%
Complexity 23799 23799
=========================================
Files 2251 2251
Lines 226874 226874
Branches 24969 24969
=========================================
Hits 114392 114392
Misses 103871 103871
Partials 8611 8611Continue to review full report at Codecov.
|
sduskis
approved these changes
May 24, 2019
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Addresses forthcoming changes to how DEADLINE_EXCEEDED is handled, a la #5198