Repository navigation
cue.py fails with KeyError 'vs2022' on GitHub Actions windows-2025-vs2026 #112
Description
Run python .ci/cue.py prepare
Clearing empty environment variable GITHUB_ACTION_REF
Clearing empty environment variable GITHUB_ACTION_REPOSITORY
Clearing empty environment variable GITHUB_BASE_REF
Clearing empty environment variable GITHUB_HEAD_REF
Traceback (most recent call last):
File "D:\a\recsync\recsync\client\.ci\cue.py", line 1477, in <module>
main(sys.argv[1:])
File "D:\a\recsync\recsync\client\.ci\cue.py", line 1471, in main
with_vcvars(' '.join(['--no-vcvars'] + raw))
File "D:\a\recsync\recsync\client\.ci\cue.py", line 1380, in with_vcvars
info['vcvars'] = vcvars_found[CC]
~~~~~~~~~~~~^^^^
KeyError: 'vs2022'
Error: Process completed with exit code 1.
with:
GITHUB_ACTIONS=trueRUNNER_OS=WindowsCMP=vs2022runs-on: windows-2025
see https://github.com/ChannelFinder/recsync/actions/runs/25477705971/job/74754707955 (or https://github.com/ChannelFinder/recsync/actions/runs/25481502523/job/74766536542 for latest version of this project)
Activity
ralphlange commentedon May 7, 2026
Meh.
Could it be the windows-2025 runner doesn't have vs2022? The doc says it does.
The title mentions vs2026 - now I'm confused.
In any case: The failure should be more explicit, I agree.
anderslindho commentedon May 7, 2026
I think we can fix with
vswhereralphlange commentedon May 7, 2026
vsWHAT?anderslindho commentedon May 7, 2026
ralphlange commentedon May 7, 2026
Jajaja.
I found the new README.
Will add the path for
vs2026as a quick fix and check outvswhatever.(Scared about backward compatibility and portability across CI services.)
Add vs2026 locations
ralphlange commentedon May 7, 2026
Please check #113 - you need to set
CMP=vs2026.anderslindho commentedon May 7, 2026
Have you tested it or do you want me to do so now? I will otherwise leave this be till merged.
ralphlange commentedon May 7, 2026
Untested.
I will update ci-scripts own tests next. The matrix needs to get more complicated...
anderslindho commentedon May 7, 2026
Doesn't seem to work, if I did things correctly:
https://github.com/ChannelFinder/recsync/actions/runs/25484117010/job/74775236272
ralphlange commentedon May 7, 2026
That's a job on
windows-2022, which doesn't havevs2026.Your matrix also needs to get more complicated.
ralphlange commentedon May 7, 2026
Should ci-scripts @windows have a default vs version?
(That would move us towards
vswherethehell.)anderslindho commentedon May 7, 2026
I don't really want my matrix to get more complicated :/
I vote for auto-detected vs version in all cases, i.e.
vswhosehouseralphlange commentedon May 7, 2026
There are runners (on other services) with multiple vs versions installed.
Suggestion:
Default loops through the locations (new -> old), takes the first one found.
Explicit setting checks only the matching locations and fails if not found.
anderslindho commentedon May 7, 2026
Maybe
vswhatsupcan handle that case neatly though? Otherwise your approach sounds good to mepheest commentedon Jul 13, 2026
I am struggling also with this issue, while seeking to use VS2022.
ralphlange commentedon Jul 13, 2026
Thanks for the reminder. I seem to have left PR #113 dangling.
Add vs2026 locations
ralphlange commentedon Jul 14, 2026
@anderslindho, @pheest: Please check #115 - I think that PR will solve your issues.
In your job settings, set the compiler to 'vs' to automatically select the installed one (if only one is installed).
I still need to check the PR on the other forges (GitLab, Appveyor) before I feel confident enough to merge.
And I need to properly document it, of course.
@anderslindho: Thanks a lot for pointing out
vswtf- not bad after all.pheest commentedon Jul 15, 2026
I am pleased to confirm that it does solve the issue.
I tested this with the compiler set to 'vs' (selected vs2026) and also set to 'vs2026'.
Add vs2026 locations