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
build python failed on test_socket due to unused_port is actually used. #73953
Comments
I am running a debian system. And trying to build cpython3.6 from source. After some trouble shooting, it seems the support.get_unused_port() is not reliable. Then I modified it and return a port I am sure no one is using, the build succeeded. |
Could you show the failure message here? And you could make your patch a PR on GitHub. |
The error message is just a "Port already used". Possible cause 1: find_port default interface is HOST, which is 127.0.0.1. And in most test cases, they use 0.0.0.0. So they are on different interface. 2: system reuse the port, since I build python on a busy server, that is possible. |
Another error message:
Unhandled exception in thread started by <bound method ThreadableTest.clientRun of <test.test_socket.NetworkConnectionAttributesTest testMethod=testSourceAddress>>
Traceback (most recent call last):
File "/tmp/python3.6/Python-3.6.0/Lib/test/test_socket.py", line 293, in clientRun
self.clientTearDown()
File "/tmp/python3.6/Python-3.6.0/Lib/test/test_socket.py", line 4379, in clientTearDown
self.cli.close()
AttributeError: 'NetworkConnectionAttributesTest' object has no attribute 'cli' |
I am sorry but it is not possible to fix the issue since we don't have enough information to identify or reproduce the bug. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: