[issue29767] build python failed on test_socket due to unused_port is actually used.

2017-03-08 Thread Shuo Li
New submission from Shuo Li: I am running a debian system. And trying to build cpython3.6 from source. When I run make altinstall, it failed on test_socket. Reporting cli attribute is missing. After some trouble shooting, it seems the support.get_unused_port() is not reliable. Then I

[issue29767] build python failed on test_socket due to unused_port is actually used.

2017-03-10 Thread Shuo Li
Shuo Li added the comment: 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 b

[issue29767] build python failed on test_socket due to unused_port is actually used.

2017-03-10 Thread Shuo Li
Shuo Li added the comment: Another error message: Unhandled exception in thread started by > 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/Pyt