Skip to content

Downgrade to windows-2022 to keep using VS2022#1984

Merged
nullsystem merged 1 commit into
NeotokyoRebuild:masterfrom
nullsystem:DowngradeToWindows2022
Jun 11, 2026
Merged

Downgrade to windows-2022 to keep using VS2022#1984
nullsystem merged 1 commit into
NeotokyoRebuild:masterfrom
nullsystem:DowngradeToWindows2022

Conversation

@nullsystem

Copy link
Copy Markdown
Collaborator

Description

See: actions/runner-images#14017

As it stands, if we keep on using windows-2025 every builds from now on will end up using VS2026 and it's hard crashing at the moment:
https://developercommunity.visualstudio.com/t/MSVC-v1451-Linker-Crash-in-IncrCalcPtrs/11090307

2026-06-10 main branch build run:
https://github.com/NeotokyoRebuild/neo/actions/runs/27300329689

This crash may only be for a short duration and VS2026 updates but still I think VS2026 is too new and isn't ready yet.

Toolchain

  • Windows MSVC VS2022
  • Windows MSVC VS2026

See: actions/runner-images#14017

As it stands, if we keep on using windows-2025 every builds
from now on will end up using VS2026 and it's hard crashing
at the moment:
https://developercommunity.visualstudio.com/t/MSVC-v1451-Linker-Crash-in-IncrCalcPtrs/11090307

2026-06-10 main branch build run:
https://github.com/NeotokyoRebuild/neo/actions/runs/27300329689

This crash may only be for a short duration and VS2026 updates
but still I think VS2026 is too new and isn't ready yet.
@nullsystem nullsystem requested a review from a team June 10, 2026 19:55
@Rainyan Rainyan added the CI Continuous Integration (GitHub Actions) label Jun 10, 2026
@Rainyan Rainyan requested a review from a team June 10, 2026 20:14
@nullsystem nullsystem merged commit 321c059 into NeotokyoRebuild:master Jun 11, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Continuous Integration (GitHub Actions) URGENT

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants