feat(tests): log operation status when calling retryForever
#636
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
jeff-held-aiven
force-pushed
the
jeff-held-aiven-log-retries
branch
2 times, most recently
from
164244d to
8f16516
Compare
To better understand what exactly failed, `retryForever` now requires that a string that contains a description of the operation be passed.
byashimov
force-pushed
the
jeff-held-aiven-log-retries
branch
from
8f16516 to
5bcbebc
Compare
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.
To better understand what exactly failed,
retryForevernow requires that a string that contains a description of the operation be passed.