Skip to content

[3.13] gh-144551: Update CI to use latest OpenSSL versions (GH-144794)#144800

Merged
zware merged 1 commit intopython:3.13from
zware:backport-b933ef9-3.13
Feb 13, 2026
Merged

[3.13] gh-144551: Update CI to use latest OpenSSL versions (GH-144794)#144800
zware merged 1 commit intopython:3.13from
zware:backport-b933ef9-3.13

Conversation

@zware
Copy link
Member

@zware zware commented Feb 13, 2026

(cherry picked from commit b933ef9)

…honGH-144794)

Also update _ssl_data_36.h to include an added symbol from 3.6.1.
(cherry picked from commit b933ef9)

Co-authored-by: Zachary Ware <zach@python.org>
@zware
Copy link
Member Author

zware commented Feb 13, 2026

Note that this backport both goes farther and not as far as the original; an update to Modules/_ssl_data_3*.h is not included, but this includes updates to the CI/multissltests versions that had not been previously backported. I'm neutral on whether to even merge this one; @hugovk or @Yhg1s?

@zware zware changed the title [3.13] gh-144551: Update CI to use latest OpenSSL versions [3.13] gh-144551: Update CI to use latest OpenSSL versions (GH-144794) Feb 13, 2026
@hugovk
Copy link
Member

hugovk commented Feb 13, 2026

I think we should at least bump the micro versions of the existing ones.

If we're going to switch to from 3.0 LTS to 3.5 LTS at some point for 3.13 (which I guess we are, with 3.0 going EOL this year?) then it makes sense to at least test up to that version.

3.5 LTS will be supported until 2030 which is enough for 3.13's lifetime.

Although it's probably okay to also test 3.6?

@zware
Copy link
Member Author

zware commented Feb 13, 2026

Ok, you (and passing CI :) ) have convinced me to go ahead with this backport. Anything beyond this will I think need Thomas's input.

@zware zware merged commit 48dd852 into python:3.13 Feb 13, 2026
46 checks passed
@zware zware deleted the backport-b933ef9-3.13 branch February 13, 2026 21:41
@bedevere-bot
Copy link

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 Debian root 3.13 (tier-1) has failed when building commit 48dd852.

What do you need to do:

  1. Don't panic.
  2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
  3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1441/builds/1779) and take a look at the build logs.
  4. Check if the failure is related to this commit (48dd852) or if it is a false positive.
  5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1441/builds/1779

Summary of the results of the build (if available):

==

Click to see traceback logs
Traceback (most recent call last):
  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/test/support/__init__.py", line 856, in gc_collect
    gc.collect()
ResourceWarning: unclosed file <_io.FileIO name=13 mode='wb' closefd=True>


Traceback (most recent call last):
  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/test/support/__init__.py", line 856, in gc_collect
    gc.collect()
ResourceWarning: unclosed file <_io.FileIO name=11 mode='wb' closefd=True>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants