Repository navigation
Label the unpinned MSVC arm64 CI leg 14.52 - #422
Conversation
The windows-11-vs2026-arm image now defaults to MSVC 14.52 and no longer installs 14.51 side by side, so the leg cannot be pinned back. The Configure MSVC step rejected the stale label on every run.
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
[Low impact] This PR appears safe to merge.
|
|
An automated preview of the documentation is available at https://422.corosio.prtest3.cppalliance.org/index.html If more commits are pushed to the pull request, the docs will rebuild at the same URL. 2026-11-16 16:53:05 UTC |
|
GCOVR code coverage report https://422.corosio.prtest3.cppalliance.org/gcovr/index.html Build time: 2026-11-16 17:12:51 UTC |
The
MSVC 14.51: C++20 (arm64)job fails on every run at the Configure MSVC step:The
windows-11-vs2026-armimage (win11-vs2026-arm64/20261112.217) ships VS 18.12, whose default toolset is 14.52. Its only side-by-side MSVC toolset is 14.44, so the leg cannot be pinned back to 14.51. This leg has nomsvc_toolsetpin and builds with the image default. The step that checks the compiler against the matrix version caught the change as intended.Changes
.github/compilers.jsonnow says 14.52. The job is renamed toMSVC 14.52: C++20 (arm64). The B2 toolset staysmsvc-14.5, and the pinned 14.44 arm64 leg is unchanged.The x64
MSVC 14.51legs onwindows-2025-vs2026are not pinned either. They will fail the same way when that image moves to 14.52.Testing
generate-matrix.pyproduces the same MSVC jobs as before, apart from the new name.Summary by CodeRabbit