Skip to content

[CI] Build on Windows: use GitHub-hosted windows-2022 CPU runner (#7443)#7555

Open
slawblauciak wants to merge 1 commit into
mainfrom
sblauciak/windows-cpu-build-7443
Open

[CI] Build on Windows: use GitHub-hosted windows-2022 CPU runner (#7443)#7555
slawblauciak wants to merge 1 commit into
mainfrom
sblauciak/windows-cpu-build-7443

Conversation

@slawblauciak

@slawblauciak slawblauciak commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Closes #7443

The Build on Windows workflow only compiles Triton and does not use a GPU,
so run it on the GitHub-hosted, CPU-only windows-2022 runner instead of the
self-hosted GPU pool. Set up MSVC via ilammy/msvc-dev-cmd (matching
llvm-build.yml) rather than a hardcoded vcvarsall.bat path, and drop the
reliance on a runner-preinstalled ninja (ninja<1.13.0 is pinned in
pyproject.toml).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@kwasd

kwasd commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Well are we OK with GH-hosted runners? I suppose they are expensive and we have our own infrastructure.

By tomorrow evening I will update this thread with a Windows runner including all our build tools, so no need to implement toolchain provisioning on each run.

@kwasd

kwasd commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

In this PR, please just separate the build step, running on our existing GPU runners.
Tomorrow we will switch this step to a new CPU runners with same environment, but without GPU.

@kwasd

kwasd commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

I need a little more time and plan to launch the runner tomorrow. I can handle also workflow changes to separate the build step.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CI] Run Windows build workflow on a CPU-only machine

2 participants