fix: wait for public e2e tunnel readiness - #116
Merged
Merged
Conversation
SUSTAPLE117
approved these changes
Sep 17, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fresh Cloudflare quick tunnels can announce a hostname before public DNS serves it. The GOAT test could deploy a payload during that window, causing the first GitHub runner callback to fail with curl exit code 6.
This change waits for both local Kitchen health and the public tunnel health endpoint. It queries public DNS directly and pins the health request with curl
--resolveto avoid stale NXDOMAIN entries in the host resolver cache. If a tunnel remains unreachable, E2E provisions a replacement and updates its runtime configuration before continuing.Validation:
make e2e-goat- passed in 187 seconds through cache poisoning, GCP pivot, and flag capturego test ./internal/ryemake -n e2e-upgit diff --check