Skip to content

Conversation

@vstinner
Copy link
Member

@vstinner vstinner commented Feb 10, 2026

Replace windows-2022 with windows-2025.

@vstinner
Copy link
Member Author

I modified a random file (Lib/test/test_dtrace.py) to trigger the Windows CIs. I will revert this TEST change once I will have the confirmation that the Windows CIs pass.

@vstinner
Copy link
Member Author

This change leaves .azure-pipelines/ci.yml unchanged, it still contains:

- job: Windows_CI_Tests
  ...
  pool:
    vmImage: windows-2022

I propose updating .azure-pipelines/ci.yml in a separated change.

@vstinner
Copy link
Member Author

See also #144679 : we might wait and upgrade directly to windows-2025-vs2026 image.

@vstinner
Copy link
Member Author

All Windows CI jobs passed successfully. Examples:

JIT / aarch64-pc-windows-msvc/msvc (Debug) (pull_request)
JIT / aarch64-pc-windows-msvc/msvc (Release) (pull_request)
JIT / i686-pc-windows-msvc/msvc (Debug) (pull_request)
JIT / i686-pc-windows-msvc/msvc (Release) (pull_request)
Tests / Windows (free-threading) / Build and test (arm64) (pull_request)
Tests / Windows (free-threading) / Build and test (x64) (pull_request)
Tests / Windows / Build and test (arm64) (pull_request)
Tests / Windows / Build and test (Win32) (pull_request)
Tests / Windows / Build and test (x64) (pull_request)
Tests / Windows MSI / installer for arm64 (pull_request)
Tests / Windows MSI / installer for x64 (pull_request)
Tests / Windows MSI / installer for x86 (pull_request)

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.

1 participant