gh-138744: GitHub Actions: pin to windows-2022#138743
Conversation
windows-22.04windows-22.04
|
Also needed in |
windows-22.04windows-2022
vstinner
left a comment
There was a problem hiding this comment.
LGTM. It's a good idea to pin the Windows version and only upgrade it once it's well tested on newer Windows.
Looks like they both do: |
|
Thanks @hugovk for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9, 3.10, 3.11, 3.12, 3.13, 3.14. |
(cherry picked from commit 6e78a53) Co-authored-by: Hugo van Kemenade <[email protected]>
|
Sorry, @hugovk, I could not cleanly backport this to |
|
Sorry, @hugovk, I could not cleanly backport this to |
|
GH-138752 is a backport of this pull request to the 3.14 branch. |
|
Sorry, @hugovk, I could not cleanly backport this to |
|
Sorry, @hugovk, I could not cleanly backport this to |
|
Sorry, @hugovk, I could not cleanly backport this to |
|
GH-138753 is a backport of this pull request to the 3.13 branch. |
…GH-138743) (cherry picked from commit 6e78a53) Co-authored-by: Hugo van Kemenade <[email protected]>
…GH-138743) (cherry picked from commit 6e78a53) Co-authored-by: Hugo van Kemenade <[email protected]>
|
GH-138754 is a backport of this pull request to the 3.12 branch. |
…GH-138743) (cherry picked from commit 6e78a53) Co-authored-by: Hugo van Kemenade <[email protected]>
|
GH-138755 is a backport of this pull request to the 3.11 branch. |
…GH-138743) (cherry picked from commit 6e78a53) Co-authored-by: Hugo van Kemenade <[email protected]>
|
GH-138757 is a backport of this pull request to the 3.10 branch. |
…H-138743) (cherry picked from commit 6e78a53) Co-authored-by: Hugo van Kemenade <[email protected]>
|
GH-138758 is a backport of this pull request to the 3.9 branch. |
…138752) Co-authored-by: Hugo van Kemenade <[email protected]>
…H-138755) * [3.11] gh-138744: GitHub Actions: pin to `windows-2022` (GH-138743) (cherry picked from commit 6e78a53) Co-authored-by: Hugo van Kemenade <[email protected]> * Update .azure-pipelines/libffi-build.yml
GitHub Actions is in the process of migrating
windows-latestfromwindows-2022towindows-2025:actions/runner-images#12677
This is causing failures for forks which have already been migrated, for example:
https://github.com/picnixz/cpython/actions/runs/17610564159/job/50031376950#step:1:9
Upstream and my fork are still on 2022, but let's pin to
windows-2022so we can separately investigate and fix for 2025, and then pin towindows-2025.test_dtracefails on Windows Server 2025 #138744