Improve machine wait and update reliability#4765
Merged
Conversation
Resolve primary and secondary regions once per process instead of re-querying per test env. Keep fallback failures as warnings and move successful auto-selection to debug logging to reduce noise.
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 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.
Change Summary
What and Why:
fly machine waitso operators can wait for a specific state or for a machine to settle.machine updatefail clearly when an update settles infailedstate.machine waitin detach deploy tests.How:
machine waitcommand with--state(defaultsettled) and--wait-timeout.failed.Related to:
Documentation