test(net): preserve UDP reservations in candidate race fixtures - #77
Merged
Merged
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
1 participant
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.
Candidate fixtures reserved/sorted ephemeral UDP ports, dropped their sockets and rebound the addresses during endpoint setup. Ubuntu workspace CI at ee1c91c hit Address already in use before reaching its identity assertions.
The fixtures now transfer their actual bound sockets through the existing owned-transport seam. Candidate order, the held blackhole socket, both families, wrong-identity rejection, authenticated winner and handshake bounds remain unchanged. No runtime API, transport behavior or binding retry is added.
Validation: all seven candidate-race tests passed on macOS; strict net/all-target/all-feature lint passed. All seven tests and strict net/all-target/all-feature lint also passed on Linux. Original CI failure is retained in issue #76 and its exact job.
Closes #76.