Extend timeout #666
Merged
Extend timeout #666
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
natebosch
approved these changes
Jul 18, 2017
|
Ooops - you 12 12.25-dev |
|
Any plans to release this? These changes seem to help some of the timeout issues I was seeing in #390. |
|
No objections from me – @grouma ? |
|
No objections from me :D |
nex3
reviewed
Sep 20, 2017
| @@ -1,3 +1,7 @@ | |||
| ## 0.12.24-dev | |||
|
|
|||
| * Extend `deserializeTimeout`. | |||
There was a problem hiding this comment.
DBC: This could be worded better. Changelog entries should generally be written to be consumed by end-users, who won't have any idea what deserializeTimeout refers to, especially when it's formatted like a Dart identifier. Something like "Time out more slowly when loading test suites" would be clearer and more user-focused.
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.
Extending deserialize timeout as it was impacting long running coverage tests within Google3.