Fixes #18548.
The solution suggested in #18548 (comment).
Also more functional tests added to the native Windows task.
Fixes #18548.
The solution suggested in #18548 (comment).
Also more functional tests added to the native Windows task.
This change should mitigate "OSError: [WinError 10048] Only one usage of
each socket address (protocol/network address/port) is normally
permitted".
concept ACK 097ac74fd22f706fb7d8d652dadea844dc8198b9
146 | @@ -147,6 +147,10 @@ task: 147 | - python test\util\test_runner.py 148 | - python test\util\rpcauth-test.py 149 | functional_tests_script: 150 | + # 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". 151 | + # See: https://docs.microsoft.com/en-us/biztalk/technical-guides/settings-that-can-be-modified-to-improve-network-performance 152 | + - netsh int ipv4 set dynamicport tcp start=1025 num=64511 153 | + - netsh int ipv6 set dynamicport tcp start=1025 num=64511
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])?
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 fab98992043f47fa7240d7c1217920d0c4f783a2 some day?
Concept ACK. Most of the latest PRs are currently failing CI because of this.