This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author paul.moore
Recipients paul.moore
Date 2007-11-22.21:23:10
SpamBayes Score 0.012548426
Marked as misclassified No
Message-id <1195766591.59.0.212085206705.issue1489@psf.upfronthosting.co.za>
In-reply-to
Content
When running the test suite on Windows, test_socket_ssl hangs.

After a bit of investigation, it appears that the test is hanging at
line 184 (if self.s.stdout.readline() != "ERROR\n":) in
OpenSSLServer._external.

The problem is that the test assumes it can read a line of stdout from
the openssl.exe process. However, the openssl.exe on my PC (from the
GnuWin32 project) appears to buffer its output, so the Python process
deadlocks waiting for a response.

An easy (if clumsy) fix is to simply skip the check on the output of the
server. I have attached a patch which does this for win32 only (on the
assumption that other platforms don't have this issue).

I guess that other openssl builds don't have the same problem - however,
I can't see an easy way of testing for this.
Files
File name Uploaded
test_socket_ssl.diff paul.moore, 2007-11-22.21:23:10
History
Date User Action Args
2007-11-22 21:23:11paul.mooresetspambayes_score: 0.0125484 -> 0.012548426
recipients: + paul.moore
2007-11-22 21:23:11paul.mooresetspambayes_score: 0.0125484 -> 0.0125484
messageid: <1195766591.59.0.212085206705.issue1489@psf.upfronthosting.co.za>
2007-11-22 21:23:11paul.moorelinkissue1489 messages
2007-11-22 21:23:10paul.moorecreate