-
Notifications
You must be signed in to change notification settings - Fork 37.7k
ci: Increase the dynamic port range to the maximum on native Windows #23089
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This change should mitigate "OSError: [WinError 10048] Only one usage of each socket address (protocol/network address/port) is normally permitted".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ack 097ac74
concept ACK 097ac74 |
# Increase the dynamic port range to the maximum allowed value to mitigate "OSError: [WinError 10048] Only one usage of each socket address (protocol/network address/port) is normally permitted". | ||
# See: https://docs.microsoft.com/en-us/biztalk/technical-guides/settings-that-can-be-modified-to-improve-network-performance | ||
- netsh int ipv4 set dynamicport tcp start=1025 num=64511 | ||
- netsh int ipv6 set dynamicport tcp start=1025 num=64511 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this mean they might collide with the p2p and rpc ports from [TEST_RUNNER_PORT_MIN, TEST_RUNNER_PORT_MIN + 2 * range]
([14000, 24000]
)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, if an ephemeral port by accident belongs to that range a collision is possible. But this range limits only ports of P2P and RPC connections. Our test framework uses ports out of this range in the feature_bind_extra.py
and feature_proxy.py
. The former is skipped on Windows, but the latter still could be a source of port collisions.
Maybe this allows to revert fab9899 some day? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Concept ACK. Most of the latest PRs are currently failing CI because of this.
…roxy fad0227 test: Remove Windows workaround in authproxy (MarcoFalke) Pull request description: Might no longer be needed after bitcoin/bitcoin#23089 ACKs for top commit: hebasto: ACK fad0227, passed 3 consequential runs on my [personal CI](https://cirrus-ci.com/task/4897456077930496): Tree-SHA512: 3c408e068ad7590dc0e5922c0b4cd3bf927e22fe624b13b8ab38db848342d310c9c934f358638fd5234c7b5f10f95d3bddc676deb925dcbba54945e2e8229275
fad0227 test: Remove Windows workaround in authproxy (MarcoFalke) Pull request description: Might no longer be needed after bitcoin#23089 ACKs for top commit: hebasto: ACK fad0227, passed 3 consequential runs on my [personal CI](https://cirrus-ci.com/task/4897456077930496): Tree-SHA512: 3c408e068ad7590dc0e5922c0b4cd3bf927e22fe624b13b8ab38db848342d310c9c934f358638fd5234c7b5f10f95d3bddc676deb925dcbba54945e2e8229275
Fixes #18548.
The solution suggested in #18548 (comment).
Also more functional tests added to the native Windows task.