Retry with backoff when waiting for a given state in app-ng tests #249
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
Previously, tests that waited for a PERSISTENT-QVM or JOB to reach a particular state would just blindly loop repeating the request and hope for the best. This commit adds a WAIT-FOR function that retries the request with an increasing backoff delay between failures.
stylewarning
approved these changes
Mar 25, 2020
Merged
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.
Previously, tests that waited for a
PERSISTENT-QVMorJOBto reach a particular state would just blindly loop repeating the request and hope for the best. This commit adds aWAIT-FORfunction that retries the request with an increasing backoff delay between failures.I don't know if http requests suddenly got faster or if something in the QVM suddenly got slower, but I noticed the wait/resume test suddenly started failing on my laptop without this change.