bpo-44229: Intest_ssl, ignore spurious EPROTOTYPE on macOS#26893
Conversation
|
Backport though to 3.9? (...maybe even 3.8, since it's breaking CI) |
Sorry, something went wrong.
Is the error happening on 3.9 and 3.8? I though this only happened in 3.10 and main |
Sorry, something went wrong.
|
I think we've just let it pass as a flakey ssl test earlier. With PEP 644, the ssl tests have been heavily scrutinised :) |
Sorry, something went wrong.
|
Also, question, in your message there are 3 different exceptions: are all of this fixed by this PR? |
Sorry, something went wrong.
|
Yes. Errno 41 always happens in the mock server set up by the test. On the client side, this results in either errno 54 or errno 61. |
Sorry, something went wrong.
|
Thanks @erlend-aasland for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.9. |
Sorry, something went wrong.
|
Thanks @erlend-aasland for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8. |
Sorry, something went wrong.
|
Thanks @erlend-aasland for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10. |
Sorry, something went wrong.
https://bugs.python.org/issue44229