Tune polling intervals for an overall faster ValidateEgress()
#260
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.
What does this PR do? / Related Issues / Jira
This PR speeds up
ValidateEgress()
but adjusting how often we're checking for serial console output (i.e., "thePollImmediate()
loop") and if the EC2 instance has finished terminating. This means that we'll spend less time unnecessarily waiting if, e.g., an instance finishes terminating after 17 seconds, as the previous config would only have checked once at 15s and again at 30s, whereas this new config will check at 3s, 6s, 9s... 15s, and 18s.Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works[ ] I have added execution results to the PR's readmeHow to test this PR locally / Special Instructions
Keep an eye out for previously unforeseen race conditions or API ratelimiting (unlikely given the still-long intervals). Otherwise, please test this PR as you would any other verifier PR.