-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test_ssl fails on recent FreeBSD (OpenSSL 1.1.1p), minimum_version=TLSv1_2 #94208
Comments
cc @koobs |
The defaults of the FreeBSD OpenSSL port/package may have changed (or I inadvertently changed them). Python tests should either either check for TLS version support in the underlying SSL library before running the tests, or skipping (not FAIL'ing) due to non-presence of the required version for the test to pass, as they cant pass a test for protocol version support that doesn't exist. Any OpenSSL library for any OS under test/CI for CPython may change support for any protocol version or feature at any time, so its worth leveling up the SSL tests in that regard. |
@pablogsal The failing tests on FreeBSD are blocking the release pipeline, https://buildbot.python.org/all/#/release_status I'm working on a fix. |
Three test cases were failing on FreeBSD with latest OpenSSL.
Three test cases were failing on FreeBSD with latest OpenSSL.
…honGH-94347) Three test cases were failing on FreeBSD with latest OpenSSL. (cherry picked from commit 1bc86c2) Co-authored-by: Christian Heimes <christian@python.org>
…honGH-94347) Three test cases were failing on FreeBSD with latest OpenSSL. (cherry picked from commit 1bc86c2) Co-authored-by: Christian Heimes <christian@python.org>
Fixed by #94347 |
FreeBSD is only a Tier3 platform on purpose: https://peps.python.org/pep-0011/#tier-3 Why is it blocking a release? Tier3 says: "Failures on these platforms do not block a release". |
The buildbot UI was showing a warning that 3.11 was not in a release-able state. I guess the release status page does not understand the difference between stable buildbot and tier 3 buildbot yet. |
@pablogsal @brettcannon: Do you have to clarify how https://buildbot.python.org/all/#/release_status treats the 3 tiers of PEP 11? |
Probably, but I didn't even know that page existed until now. 😅 My guess is it blindly relies on stable buildbots instead of the tier labels. |
Yep, it's a simple boolean test: STABLE vs "not STABLE" workers. |
I'd like to take the opportunity to put out a explicit call for a second core maintainer to promote FreeBSD to Tier 2 on the following basis:
|
…honGH-94347) Three test cases were failing on FreeBSD with latest OpenSSL.
…honGH-94347) Three test cases were failing on FreeBSD with latest OpenSSL. (cherry picked from commit 1bc86c2)
pythonGH-94347) Three test cases were failing on FreeBSD with latest OpenSSL. (cherry picked from commit 1bc86c2) Co-authored-by: Christian Heimes <christian@python.org>
…honGH-94347) Three test cases were failing on FreeBSD with latest OpenSSL. (cherry picked from commit 1bc86c2)
pythonGH-94347) Three test cases were failing on FreeBSD with latest OpenSSL. (cherry picked from commit 1bc86c2) Co-authored-by: Christian Heimes <christian@python.org>
…honGH-94347) Three test cases were failing on FreeBSD with latest OpenSSL. (cherry picked from commit 1bc86c2)
pythonGH-94347) Three test cases were failing on FreeBSD with latest OpenSSL. (cherry picked from commit 1bc86c2) Co-authored-by: Christian Heimes <christian@python.org>
test_ssl started to fail today on AMD64 FreeBSD Shared 3.x:
https://buildbot.python.org/all/#/builders/483/builds/2643
It seems like ssl.SSLContext.minimum_version is now TLSVersion.TLSv1_2.
test.pythoninfo:
The text was updated successfully, but these errors were encountered: