cue.py fails with KeyError 'vs2022' on GitHub Actions windows-2025-vs2026

[anderslindho]

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=true
• RUNNER_OS=Windows
• CMP=vs2022
• runs-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)

[ralphlange]

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]

I think we can fix with vswhere

[ralphlange]

vsWHAT?

[anderslindho]

Detecting existing Visual Studio instances
The following tools and utilities will help you detect and manage installed Visual Studio instances on client machines:

• vswhere: an executable built into Visual Studio or available for separate distribution that helps you find the location of all Visual Studio instances on a particular machine.

[ralphlange]

Jajaja.

I found the new README.
Will add the path for vs2026 as a quick fix and check out vswhatever.
(Scared about backward compatibility and portability across CI services.)

[ralphlange]

Please check #113 - you need to set CMP=vs2026.

[anderslindho]

Have you tested it or do you want me to do so now? I will otherwise leave this be till merged.

[ralphlange]

Untested.
I will update ci-scripts own tests next. The matrix needs to get more complicated...

[anderslindho]

Doesn't seem to work, if I did things correctly:

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 1514, in <module>
    main(sys.argv[1:])
  File "D:\a\recsync\recsync\client\.ci\cue.py", line 1508, in main
    with_vcvars(' '.join(['--no-vcvars'] + raw))
  File "D:\a\recsync\recsync\client\.ci\cue.py", line 1415, in with_vcvars
    info['vcvars'] = vcvars_found[CC]
                     ~~~~~~~~~~~~^^^^
KeyError: 'vs2026'
Error: Process completed with exit code 1.

https://github.com/ChannelFinder/recsync/actions/runs/25484117010/job/74775236272

[ralphlange]

That's a job on windows-2022, which doesn't have vs2026.
Your matrix also needs to get more complicated.

[ralphlange]

Should ci-scripts @windows have a default vs version?
(That would move us towards vswherethehell.)

[anderslindho]

I don't really want my matrix to get more complicated :/

I vote for auto-detected vs version in all cases, i.e. vswhosehouse