Skip to content

[codex] package Windows ARM64 on x64#28001

Merged
tamird merged 1 commit into
mainfrom
codex/package-windows-arm64-on-x64
Jun 13, 2026
Merged

[codex] package Windows ARM64 on x64#28001
tamird merged 1 commit into
mainfrom
codex/package-windows-arm64-on-x64

Conversation

@tamird

@tamird tamird commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

The first release after parallelizing Windows packaging moved the
critical path to the ARM64 packaging job:

https://github.com/openai/codex/actions/runs/27451157324

The x64 job started immediately and finished in 5m29s. The ARM64
job waited 76s for its runner and then took 5m56s, holding the
release for 1m43s after x64 had finished.

Packaging only downloads, signs, archives, and compresses already
built binaries. It does not execute target code. Run both packaging
jobs on x64 runners, keeping ARM64 hardware for compilation.

The first release after parallelizing Windows packaging moved the
critical path to the ARM64 packaging job:

https://github.com/openai/codex/actions/runs/27451157324

The x64 job started immediately and finished in 5m29s. The ARM64
job waited 76s for its runner and then took 5m56s, holding the
release for 1m43s after x64 had finished.

Packaging only downloads, signs, archives, and compresses already
built binaries. It does not execute target code. Run both packaging
jobs on x64 runners, keeping ARM64 hardware for compilation.
path: codex-rs/symbols-dist/${{ matrix.target }}/*
if-no-files-found: error

build-windows:

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is pretty confusing that this is called build-windows when it does everything except build

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah i'm guessing this was a casualty of some successive refactors here, i'd support a followup to pick a better name that isn't shadowed by the alias the release.yml file uses for this whole workflow. maybe something like assemble-and-upload-artifacts or similar? cc @bolinfest

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let me know either here or in slack if you want that followup. until then, does this LGTY?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh sorry, thought I approved when I left this comment. Michael's OOO for a bit anyways and I hadn't realized when I commented so not worth blocking on his input. Don't worry about the follow-up for now, I'm still pretty new and not sure I can check all the places where I'd want to find out it's load bearing.

@tamird
tamird enabled auto-merge (squash) June 13, 2026 01:35

@anp-oai anp-oai left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For posterity: putting together the arm64 release archives on an x86_64 machine should be safe, we're not actually doing any cross compilation or host-specific work here.

@tamird
tamird merged commit 17586d8 into main Jun 13, 2026
31 checks passed
@tamird
tamird deleted the codex/package-windows-arm64-on-x64 branch June 13, 2026 19:55
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 13, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants