[issue35352] test_asyncio fails on RHEL8, or on Fedora using NEXT security policy

STINNER Victor added the comment: I tested on Fedora 29 using: sudo update-crypto-policies --set NEXT With this config, I was able to reproduce the test_asyncio failure on 3.6, 3.7 and master branches. I confirm that the commits fixed test_asyncio in these 3 branches. Thanks

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: I leave the issue open until someone validates manually that the issue os fixed in all branches with stricter security (ex: RHEL8). -- ___ Python tracker

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: New changeset 02250e57c37339ea6de08ab077a307e75eef02f5 by Victor Stinner in branch '3.6': bpo-35352: test_asyncio uses the certificate set from the test directory (GH-10826) (GH-10832)

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: New changeset 38bed786a219c65d5a51c7ef4ffd97e12653a095 by Victor Stinner in branch '3.7': [3.7] bpo-35352: test_asyncio uses the certificate set from the test directory (GH-10826) (GH-10834)

[issue35352] test_asyncio fails on RHEL8

Change by STINNER Victor : -- pull_requests: +10073 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: New changeset 7212148c95947b0fdfcb0c8e37d4357287bdb4bd by Victor Stinner in branch 'master': bpo-35352: Cleanup test_asyncio/utils.py (GH-10831) https://github.com/python/cpython/commit/7212148c95947b0fdfcb0c8e37d4357287bdb4bd --

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: > IIRC two copies exist from very early development times when asyncio was not > a part of Python stdlib. Yeah, that was my guess as well. Maybe data_file() could be simplified or replaced by support.findfile(), but I chose the easy solution (minimize

[issue35352] test_asyncio fails on RHEL8

Andrew Svetlov added the comment: IIRC two copies exist from very early development times when asyncio was not a part of Python stdlib. -- ___ Python tracker ___

[issue35352] test_asyncio fails on RHEL8

Change by STINNER Victor : -- pull_requests: +10072 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35352] test_asyncio fails on RHEL8

Change by STINNER Victor : -- pull_requests: +10071 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35352] test_asyncio fails on RHEL8

Change by miss-islington : -- pull_requests: +10070 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: New changeset b062ba77b617b0f89b7ea25d14cc77c991462ad4 by Victor Stinner (stratakis) in branch 'master': bpo-35352: test_asyncio uses the certificate set from the test directory (GH-10826)

[issue35352] test_asyncio fails on RHEL8

Charalampos Stratakis added the comment: Also on Fedora the same set of security policies can be set as RHEL8 by utilizing 'update-crypto-policies --set NEXT' -- ___ Python tracker

[issue35352] test_asyncio fails on RHEL8

STINNER Victor added the comment: > The strange thing is these tests are passed on our build bots. RHEL8 has a very strict security policy by default. I'm not sure if any OS run on buildbot has a security policy as strict as RHEL8? > Maybe bumping used protocol version will help to pass

[issue35352] test_asyncio fails on RHEL8

Change by Charalampos Stratakis : -- keywords: +patch pull_requests: +10067 stage: -> patch review ___ Python tracker ___ ___

[issue35352] test_asyncio fails on RHEL8

Charalampos Stratakis added the comment: I believe I figured out the issue, at least on the master branch. While checking the certificates used by asyncio tests within the test_asyncio folder I noticed they were quite outdated when compared to the more recent updated ones with the test/

[issue35352] test_asyncio fails on RHEL8

Andrew Svetlov added the comment: Maybe this is the reason. asycio test suite uses these ssl contexts: https://github.com/python/cpython/blob/master/Lib/test/test_asyncio/utils.py#L72-L92 Maybe bumping used protocol version will help to pass tests on your box. Would you try it? --

[issue35352] test_asyncio fails on RHEL8

Charalampos Stratakis added the comment: It seems I can reproduce it on Fedora as well by setting stronger crypto defaults through 'update-crypto-policies --set FUTURE'. Repo located here: https://gitlab.com/redhat-crypto/fedora-crypto-policies/tree/master The changes are many, but if I

[issue35352] test_asyncio fails on RHEL8

Andrew Svetlov added the comment: The strange thing is these tests are passed on our build bots. In logs I see only ConnectionResetError. Can it be related to your configuration? -- ___ Python tracker

[issue35352] test_asyncio fails on RHEL8

Change by Charalampos Stratakis : Added file: https://bugs.python.org/file47957/asyncio_failures_3.6.log ___ Python tracker ___ ___

[issue35352] test_asyncio fails on RHEL8

Charalampos Stratakis added the comment: Seems that 3.8 and 3.7 get the same failures, while 3.6 gets 14 instead of 8. -- ___ Python tracker ___

[issue35352] test_asyncio fails on RHEL8

New submission from Charalampos Stratakis : When compiling python3 on RHEL8 and run the tests, test_asyncio fails with 8 failures (and more on older branches). openssl version is 1.1.1 Attaching the failures for the various branches. -- components: Tests, asyncio files:

[issue35352] test_asyncio fails on RHEL8

Change by Charalampos Stratakis : Added file: https://bugs.python.org/file47956/asyncio_failures_3.7.log ___ Python tracker ___ ___