[issue28689] OpenSSL 1.1.0c test failures

Dima Tisnek added the comment: 1.1.0d is due today. Who wants to test it? :) -- nosy: +Dima.Tisnek ___ Python tracker ___

[issue28689] OpenSSL 1.1.0c test failures

Christian Heimes added the comment: Thanks, Ned! To clarify, it's not jus the test suite. OpenSSL 1.1.0c broke the ssl module. -- ___ Python tracker ___

[issue28689] OpenSSL 1.1.0c test failures

Ned Deily added the comment: I added the following text to the "Notes on this release" section for the 3.6.0rc1 release page and will copy it to future 3.6.x release pages until sometime after a fixed 1.1.0 is released: "If you are building Python from source, beware that the OpenSSL 1.1.0c

[issue28689] OpenSSL 1.1.0c test failures

Christian Heimes added the comment: No blacklisting :) I don't want to mess with any code prior to the final release of Python 3.6.0. Let's just document that stock 1.1.0c is not compatible. Ned, I'm setting the release blocker flag as a reminder to add a comment to the release notes of

[issue28689] OpenSSL 1.1.0c test failures

Matthias Klose added the comment: Fyi, Debian's 1.1.0c is fixed, so please don't blacklist this version in general. -- nosy: +doko ___ Python tracker

[issue28689] OpenSSL 1.1.0c test failures

Christian Heimes added the comment: The test suite is passing with OpenSSL 1.1.0d-dev (OpenSSL_1_1_0-stable branch). I consider 1.1.0c a broken and unsupported release. -- ___ Python tracker

[issue28689] OpenSSL 1.1.0c test failures

Charalampos Stratakis added the comment: Tested this in Fedora Rawhide virtual machine, where the fix for the problematic openssl commit was backported, and now the tests hang at test_poplib. Exception in thread Thread-982: Traceback (most recent call last): File

[issue28689] OpenSSL 1.1.0c test failures

Charalampos Stratakis added the comment: Fixed upstream: https://github.com/openssl/openssl/commit/beacb0f0c1ae7b0542fe053b95307f515b578eb7 -- nosy: +cstratak ___ Python tracker

[issue28689] OpenSSL 1.1.0c test failures

Christian Heimes added the comment: OpenSSL upstream bug: https://github.com/openssl/openssl/issues/1919 -- ___ Python tracker ___

[issue28689] OpenSSL 1.1.0c test failures

Christian Heimes added the comment: https://github.com/openssl/openssl/commit/122580ef71e4e5f355a1a104c9bfb36feee43759 -- ___ Python tracker ___

[issue28689] OpenSSL 1.1.0c test failures

Christian Heimes added the comment: A git bisect between OpenSSL_1_1_0b (good) and OpenSSL_1_1_0c (bad) revealed the breaking commit: $ git bisect good 122580ef71e4e5f355a1a104c9bfb36feee43759 is the first bad commit commit 122580ef71e4e5f355a1a104c9bfb36feee43759 Author: Matt Caswell

[issue28689] OpenSSL 1.1.0c test failures

Christian Heimes added the comment: test_server_accept (test.test_ssl.ThreadedTests) ... Exception in thread Thread-348: Traceback (most recent call last): File "/home/heimes/dev/python/cpython/Lib/threading.py", line 916, in _bootstrap_inner self.run() File

[issue28689] OpenSSL 1.1.0c test failures

Changes by Chi Hsuan Yen : -- nosy: +Chi Hsuan Yen ___ Python tracker ___ ___

[issue28689] OpenSSL 1.1.0c test failures

New submission from Christian Heimes: OpenSSL 1.1.0c broke a bunch of tests. The same tests are passing fine with OpenSSL 1.1.0 to 1.1.0b. It looks like a problem with EOF / connection close error. I'm seeing similar problems in MIT KRB5's OpenSSL plugin, too.