| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
#25361 addresses the unrelated test failures. |
Sorry, something went wrong.
There was a problem hiding this comment.
Don't we have an accepted PEP which requires OpenSSL 1.1.1 or newer?
Each additional CI increases the error rate since we still have unstable tests in asyncio and multiprocessing tests. I would prefer to not add too many CIs. At least, don't make them mandatory (allow to merge a PR even if they fail).
Rather than pre-commit CI jobs run on every since PR and at every PR update, can't we use a post-commit CI, like a buildbot worker? Issues in pre-commit are way more annoying.
cc @pablogsal @zware
Sorry, something went wrong.
There was a problem hiding this comment.
Don't we have an accept PEP which requires OpenSSL 1.1.1 or newer?
Yes, but the PEP applies to 3.10 only. You want OpenSSL 3.0.0 compatibility in 3.8 and 3.9, don't you?
Rather than pre-commit CI jobs run on every since PR and at every PR update, can't we use a post-commit CI, like a buildbot worker? Issues in pre-commit are way more annoying.
I need an easy and reliable way to ensure that Python works with all supported OpenSSL versions. Post-commit CI is too late.
Sorry, something went wrong.
There was a problem hiding this comment.
You can add OpenSSL < 1.1.1 in the CI jobs when you backport this PR to 3.9 and older. But this PR targets master, so I expect not see OpenSSL < 1.1.1 in this branch.
Sorry, something went wrong.
There was a problem hiding this comment.
Master still supports OpenSSL 1.1.0 and 1.0.2. I have not finished and pushed the PEP 644 PR. I deliberately postponed PEP 644 changes until OpenSSL 3.0.0 support is done.
Sorry, something went wrong.
There was a problem hiding this comment.
Each additional CI increases the error rate since we still have unstable tests in asyncio and multiprocessing tests. I would prefer to not add too many CIs. At least, don't make them mandatory (allow to merge a PR even if they fail).
The additional SSL tests are now only executed when any OpenSSL or GHA related file is modified. The SSL tests only execute a couple of selected tests. Multiprocessing tests are skipped. The CI steps are not mandatory.
Sorry, something went wrong.
There was a problem hiding this comment.
"Master still supports OpenSSL 1.1.0 and 1.0.2. I have not finished and pushed the PEP 644 PR. I deliberately postponed PEP 644 changes until OpenSSL 3.0.0 support is done."
Ok.
Sorry, something went wrong.
There was a problem hiding this comment.
Please don't add a new CI until all issues are fixed, like this one:
"GitHub Actions / Ubuntu SSL tests with OpenSSL 3.0.0-alpha14
‘ERR_func_error_string’ is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]"
Sorry, something went wrong.
This is a chicken and egg problem. #25329 needs this PR to verify that the code works. |
Sorry, something went wrong.
I'm spending a lot of time to fix every single warning in Python. I would prefer to not add new warnings, especially if you know that a lot of will be needed to fix them. Can't you run this CI job locally, fix warnings, and then automate checks on PRs? I would prefer not annoy contributors who don't work on OpenSSL support with these new deprecation warnings. |
Sorry, something went wrong.
I prefer to add CI first, so I have a stable baseline. Then I can fix deprecation warnings. |
Sorry, something went wrong.
|
I have added a new check_source instruction. The additional OpenSSL tests are skipped unless the commit touches any file with ssl, hmac, hashlib or ^.github in the file name. |
Sorry, something went wrong.
Signed-off-by: Christian Heimes <christian@python.org>
|
@vstinner @pablogsal I have reworked the PR. Additional checks are optional and only executed when GHA detects a modification of an OpenSSL-related file or a file in .github directory. I'm postponing PEP 644 PR until I have finalized OpenSSL 3.0.0 support. It should be ready by next week. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM.
Additional checks are optional and only executed when GHA detects a modification of an OpenSSL-related file
Ok, I'm fine with this PR in this case.
Sorry, something went wrong.
There was a problem hiding this comment.
"Master still supports OpenSSL 1.1.0 and 1.0.2. I have not finished and pushed the PEP 644 PR. I deliberately postponed PEP 644 changes until OpenSSL 3.0.0 support is done."
Ok.
Sorry, something went wrong.
|
Thanks @tiran for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9. |
Sorry, something went wrong.
The new checks are only executed when one or more OpenSSL-related files are modified. The checks run a handful of networking and hashing test suites. All SSL checks are optional. This PR also introduces ccache to speed up compilation. In common cases it speeds up configure and compile time from about 90 seconds to less than 30 seconds. Signed-off-by: Christian Heimes <christian@python.org> (cherry picked from commit 8fa1489) Co-authored-by: Christian Heimes <christian@python.org>
|
GH-25391 is a backport of this pull request to the 3.9 branch. |
Sorry, something went wrong.
The new checks are only executed when one or more OpenSSL-related files are modified. The checks run a handful of networking and hashing test suites. All SSL checks are optional. This PR also introduces ccache to speed up compilation. In common cases it speeds up configure and compile time from about 90 seconds to less than 30 seconds. Signed-off-by: Christian Heimes <christian@python.org> (cherry picked from commit 8fa1489) Co-authored-by: Christian Heimes <christian@python.org>
|
GH-25392 is a backport of this pull request to the 3.8 branch. |
Sorry, something went wrong.
…-25391) The new checks are only executed when one or more OpenSSL-related files are modified. The checks run a handful of networking and hashing test suites. All SSL checks are optional. This PR also introduces ccache to speed up compilation. In common cases it speeds up configure and compile time from about 90 seconds to less than 30 seconds. Signed-off-by: Christian Heimes <christian@python.org> (cherry picked from commit 8fa1489) Co-authored-by: Christian Heimes <christian@python.org> Automerge-Triggered-By: GH:tiran
…-25392) The new checks are only executed when one or more OpenSSL-related files are modified. The checks run a handful of networking and hashing test suites. All SSL checks are optional. This PR also introduces ccache to speed up compilation. In common cases it speeds up configure and compile time from about 90 seconds to less than 30 seconds. Signed-off-by: Christian Heimes <christian@python.org> (cherry picked from commit 8fa1489) Co-authored-by: Christian Heimes <christian@python.org> Automerge-Triggered-By: GH:tiran
| Back | FazBrowse Home | New Git URL |
The new checks are only executed when one or more OpenSSL-related files are modified. The checks run a handful of networking and hashing test suites. All SSL checks are optional. This PR also introduces ccache to speed up compilation. In common cases it speeds up configure and compile time from about 90 seconds to less than 30 seconds.
Signed-off-by: Christian Heimes christian@python.org
https://bugs.python.org/issue43811
Automerge-Triggered-By: GH:tiran