fix(run): alternate DNS stub port allocation - #490
Draft
LukeMathWalker wants to merge 2 commits into
Draft
Conversation
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.
Why
Windows maintains independent TCP and UDP excluded-port ranges. The host DNS stub could repeatedly choose TCP ports that UDP rejects with
WSAEACCES, causing otherwise unrelated Windows CI jobs to fail, as seen in this run.What Changed
Risks / Notes
The failure depends on Windows-specific excluded-port configuration and cannot be reproduced in the Linux development environment. The existing cross-platform tests exercise startup, shutdown, loopback binding, and DNS responses over both UDP and TCP; Windows CI provides the platform-specific regression coverage.