Use Namespace runners for applicable Windows builds - #1256
Open
zaniebot wants to merge 4 commits into
Open
Conversation
Use the established Windows Server 2022 profile for the x86 and x86-64 distribution builds and the x86-64 crate build.
zaniebot
force-pushed
the
namespace-windows
branch
from
September 9, 2026 22:20
78db7d4 to
5b36002
Compare
zanieb
marked this pull request as ready for review
September 10, 2026 13:59
zanieb
reviewed
Sep 10, 2026
jjhelmus
approved these changes
Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Windows distribution builds currently use Depot, while the
pythonbuildcrate runs on GitHub-hosted runners. Move the VS 2022 x86 and x86-64 distribution builds to the existingnamespace-profile-windows-2022-x86-64-16x32profile. Use the same runner lookup for crate builds, selecting Namespace for x86-64 and the nativewindows-11-armrunner for ARM64. ARM64 distributions and the x86-64 Python 3.15 builds that require VS 2026 continue to use their existing GitHub runners.Five independent successful executions per workload and side compare
5b36002dwith pinnedmainat3fb62eb4. The x86-64Buildstep is 10.6% faster; the i686 interval includes no change. Durations below are geometric means inm:ss; changes are relative tomain, with unpaired Welch t 90% confidence intervals on log runtime.i686Buildi686x86_64Buildx86_64The comparison is
depot-windows-2022-8versusnamespace-profile-windows-2022-x86-64-16x32, so it measures the provider, runner size, and image together. Both select Windows 2022/VS 2022, but neither provider records a precise OS-image release in the accepted job setup logs. The source differs only in runner selection. Whole-job timing excludes queue and dependency wait, and includesGenerate attestationsonly onmain. Cachedpythonbuildcrate builds are outside these CPython measurements.Runtime samples
Each link gives the attempt number and
Build/whole-job duration inm:ss. Untouched jobs copied into later partial reruns are counted once.i686i686x86_64x86_64The failed i686 Cygwin download was retried and excluded from the runtime samples.