[Python-Dev] Trying to build from source, test-poplib fails (original) (raw)

Christian Heimes christian at python.org
Mon Apr 9 06:01:37 EDT 2018

On 2018-04-09 10:30, Serhiy Storchaka wrote:

I get the same issues too, and this has been happening for quite some time.  The tests and/or poplib itself may be written in a fragile way. I get the different issue with testpoplib (running with the -j option). All tests except testmultiprocessingfork are passed, and testpoplib hangs. I thought it is a misconfiguration on my computer.

It's not your computer, it's the test suite. It uses the old asyncore library. The test has become unstable since the ssl module properly checks host names, see https://bugs.python.org/issue32706 and https://bugs.python.org/issue32753.

In Python 3.6 and earlier, a hostname verification error resulted in a closed connection. Starting with Python 3.7, the ssl module checks the hostname earlier in the TLS handshake. A verification error results in a TLS handshake alert and an exception on the server side. Sometimes the old server code in asyncore runs into a race condition and the test fails.

The whole test framework needs to be rewritten from scratch and replaced with something better. I haven't had time to work on it.

Christian

More information about the Python-Dev mailing list