windows-artifacts: the win-arm64 job uses a Visual Studio generator missing from windows-11-arm
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 86/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- c, cmake, github-actions
- Domain
- build-system, ci-cd
Research direction
Read windows-artifacts.yml and compare the win-arm64 CMake generator with the one already used in cmake-tests.yml. Change it to match, then verify with a push to test_artifacts as the issue requests. Done means the win-arm64 job configures successfully with the runner's installed Visual Studio.
Written by the indexing model from the issue text.
Description
The win-arm64 job of windows-artifacts.yml configures CMake with -G "Visual Studio 17 2022", but the windows-11-arm image now ships only Visual Studio 2026. The last run of this workflow (run 44396122729, 2026-11-18) fails at configuration:
CMake Error at CMakeLists.txt:30 (project):
Generator
Visual Studio 17 2022
could not find any instance of Visual Studio.
cmake-tests.yml was already switched to Visual Studio 18 2026 for the same runner in 2c2a6216e, but windows-artifacts.yml was not.
This workflow only runs on pushes to test_artifacts, win_artifacts and release, and on published releases, so the failure would first show up at the next release. With the default fail-fast, it also cancels the win32 and win64 jobs (as in run 43975850626), so that release could ship without any Windows package.
Fix: use the same generator as cmake-tests.yml, and check with a push to test_artifacts. Running this workflow on PRs that touch lib/dll/example/ or the workflow itself would catch this kind of breakage earlier.
Related: #4395.
- Dominant language
- C
- Stars
- 28.1k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from facebook/zstd
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
ZSTD_decompressStream accepts a Compressed_Block with Block_Size 0 that ZSTD_decompress rejectsPossibly taken @Artyx71 claimed this 8 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
fileio: use the prefixed lz4frame type LZ4F_contentChecksum_tPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
-
One-shot decoding refuses some skippable framesPossibly taken @ceedot-rock claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
`ZSTD_getDictID_fromFrame` returns a skippable frame's magic variant as its dictionary IDPossibly taken @b84330808 claimed this 14 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
isolation2 lockmodes fails on cassert builds: extra AccessShareLock on partition rootPossibly taken @tuhaihe claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/cloudberry#2356 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
wasm-micro-runtime/wasm-micro-runtime#5217 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HandBrake/HandBrake#8278 · 1 comment ·
Maintainers usually reply within 1 day