[issue19919] SSL: test_connect_ex_error fails with EWOULDBLOCK

2016-01-07 Thread Martin Panter
Changes by Martin Panter : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue19919] SSL: test_connect_ex_error fails with EWOULDBLOCK

2014-07-12 Thread Mark Lawrence
Mark Lawrence added the comment: Accidentally set to pending? -- nosy: +BreamoreBoy status: pending -> open ___ Python tracker ___ ___

[issue19919] SSL: test_connect_ex_error fails with EWOULDBLOCK

2013-12-16 Thread Christian Heimes
Christian Heimes added the comment: Thanks! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> pending ___ Python tracker ___

[issue19919] SSL: test_connect_ex_error fails with EWOULDBLOCK

2013-12-16 Thread Roundup Robot
Roundup Robot added the comment: New changeset 40955ae17472 by Christian Heimes in branch '3.3': Issue #19919: Fix flacky SSL test. connect_ex() sometimes returns http://hg.python.org/cpython/rev/40955ae17472 New changeset 593c3fa7aa2c by Christian Heimes in branch 'default': Issue #19919: Fix f

[issue19919] SSL: test_connect_ex_error fails with EWOULDBLOCK

2013-12-16 Thread Antoine Pitrou
Antoine Pitrou added the comment: Looks fine to me. -- stage: -> patch review versions: +Python 3.3 ___ Python tracker ___ ___ Python

[issue19919] SSL: test_connect_ex_error fails with EWOULDBLOCK

2013-12-16 Thread Christian Heimes
Christian Heimes added the comment: Here is a patch. -- keywords: +patch Added file: http://bugs.python.org/file33168/issue19919.patch ___ Python tracker ___

[issue19919] SSL: test_connect_ex_error fails with EWOULDBLOCK

2013-12-07 Thread Merlijn van Deen
Merlijn van Deen added the comment: OK. I did some network sniffing; inside the VM, this is what I see: $ sudo tshark host 82.94.164.164 tshark: Lua: Error during loading: [string "/usr/share/wireshark/init.lua"]:45: dofile has been disabled Running as user "root" and group "root". This could b

[issue19919] SSL: test_connect_ex_error fails with EWOULDBLOCK

2013-12-07 Thread Antoine Pitrou
Antoine Pitrou added the comment: The explanation for EAGAIN is in the test just above (test_timeout_connect_ex). Read it. -- nosy: +pitrou ___ Python tracker ___ __

[issue19919] SSL: test_connect_ex_error fails with EWOULDBLOCK

2013-12-07 Thread Merlijn van Deen
Merlijn van Deen added the comment: Yes, they are. >>> errno.EWOULDBLOCK 11 EAGAIN and EWOULDBLOCK are the only two with that errno: >>> [(k,v) for (k,v) in errno.__dict__.items() if v==11] [('EWOULDBLOCK', 11), ('EAGAIN', 11)] 111 is just ECONNREFUSED: >>> [(k,v) for (k,v) in errno.__dict__.i

[issue19919] SSL: test_connect_ex_error fails with EWOULDBLOCK

2013-12-07 Thread Christian Heimes
Christian Heimes added the comment: EAGAIN Resource temporarily unavailable (may be the same value as EWOULDBLOCK) (POSIX.1) Can you please check of EAGAIN and EWOULDBLOCK are the same value on your Linux box? They are the same on my box: >>> import errno >>> errno.EAGAIN, errno.EWOU

[issue19919] SSL: test_connect_ex_error fails with EWOULDBLOCK

2013-12-07 Thread Merlijn van Deen
Merlijn van Deen added the comment: My error is slightly different: $ ./python -i -c "from test.test_ssl import *; support.run_unittest(NetworkedTests)" (...) == FAIL: test_connect_ex_error (test.test_ssl.NetworkedTests) -

[issue19919] SSL: test_connect_ex_error fails with EWOULDBLOCK

2013-12-07 Thread Christian Heimes
New submission from Christian Heimes: On Windows the test_connect_ex_error sometimes fails with EWOULDBLOCK instead of ECONNREFUSED. Valhallasw sometimes gets the same error with an Ubuntu VM on Windows. This might be a Windows socket issue. ===