Skip to content

Conversation

hebasto
Copy link
Member

@hebasto hebasto commented Sep 24, 2021

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".
Copy link

@vincenzopalazzo vincenzopalazzo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ack 097ac74

@maflcko
Copy link
Member

maflcko commented Sep 25, 2021

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
Copy link
Member

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])?

Copy link
Member Author

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.

@maflcko
Copy link
Member

maflcko commented Sep 25, 2021

Maybe this allows to revert fab9899 some day?

Copy link
Member

@darosior darosior left a 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.

@maflcko maflcko merged commit 747f91c into bitcoin:master Sep 25, 2021
@hebasto hebasto deleted the 210924-portrange branch September 25, 2021 07:34
maflcko pushed a commit to bitcoin-core/gui that referenced this pull request Sep 27, 2021
…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
sidhujag pushed a commit to syscoin/syscoin that referenced this pull request Sep 27, 2021
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
@bitcoin bitcoin locked and limited conversation to collaborators Oct 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
4 participants