[issue1489] test_socket_ssl hanhs on Windows (deadlock)
Trent Nelson
report at bugs.python.org
Tue Apr 8 16:00:54 CEST 2008
Trent Nelson <tnelson at onresolve.com> added the comment:
Re-assigned this to myself (hope you don't mind janssen ;-) as I'm
actively looking into it. We build openssl.exe as part of our Windows
build so we should make an effort to use this where possible. Note
that there is definitely a problem with 'openssl s_server' on Windows,
I'm not sure if it's to do with buffering though as I can step through
the same actions the test is performing in the console and I
get 'ERROR\n' immediately back from the server. This sort of falls
into my existing work with issue 2550 (and patches) to improve network-
oriented tests such that they can be ran in parallel. Note that patch
trunk.2550-2.patch attached to issue2550 goes as far as converting
openssl to use the -accept [port] option such that we don't bind on
4443 by default (thus impeding other test_ssl_socket tests that may be
running).
Also, openssl.exe in the s_server mode is using SO_REUSEADDR when it
should be using SO_EXCLUSIVEADDRUSE. That's not our problem per se,
but given that we maintain our own openssl-0.9.8g sources, I'm
considering fixing it if it improves the reliability of the test.
(I'll feed back any changes to the OpenSSL project, of course.)
----------
assignee: janssen -> Trent.Nelson
nosy: +Trent.Nelson
__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue1489>
__________________________________
More information about the Python-bugs-list
mailing list