Uh oh!
There was an error while loading. Please reload this page.
Adding retry for bucket creation to logging system test. - #2307
Merged
Conversation
Sometimes when tests run quicker than usual or multiple builds run tests at once, the backend gives a 429 response to rate-limit our clients using one service account.
dhermesforce-pushed
the
logging-flaky-sys-test
branch
from
September 13, 2016 01:27
593e9cd to
7eb3177Compare
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Sometimes when tests run quicker than usual or multiple builds run tests at once, the backend gives a 429 response to rate-limit our clients using one service account.
I took down a bunch of failures last week and can't track down where this occurred, sorry.