roachtest: deflake acceptance/status-server #29492
Merged
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
Use a retry loop for retrieving status details right after node startup as we might be talking to the node before it is responding to the status endpoint. Release note: None
|
This change is |
|
I've seen |
tbg
approved these changes
Sep 4, 2018
|
bors r=tschottdorf |
craig bot
pushed a commit
that referenced
this pull request
Sep 4, 2018
29492: roachtest: deflake acceptance/status-server r=tschottdorf a=petermattis Use a retry loop for retrieving status details right after node startup as we might be talking to the node before it is responding to the status endpoint. Release note: None Co-authored-by: Peter Mattis <[email protected]>
Build succeeded |
This was referenced Sep 4, 2018
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.
Use a retry loop for retrieving status details right after node startup
as we might be talking to the node before it is responding to the status
endpoint.
Release note: None