[codex] pipeline Windows targets separately#28151
Open
tamird wants to merge 1 commit into
Open
Conversation
The Windows release workflow builds x64 and ARM64 in one matrix. Each target's packaging job therefore waits for all six matrix cells, even though it consumes artifacts from only the three cells for its target. In alpha.19, ARM64's builds completed at 01:40:38 UTC, but its packaging job was not created until x64 completed at 01:51:42 UTC. It then entered the x64 runner queue alongside x64 packaging. https://github.com/openai/codex/actions/runs/27484551090 Invoke the reusable workflow once per target. Each invocation retains the three bundle builds and starts symbol and package jobs as soon as those target-specific builds finish. ARM64 packaging took 6m05s on ARM in alpha.18 and 6m08s on x64 in alpha.19. Keep packaging on each target's build runner. The 11-minute ARM64 lead absorbs its runner queue and avoids consuming x64 capacity alongside the critical x64 package.
tamird
force-pushed
the
codex/pipeline-windows-targets
branch
from
4e82257 to
daa90ac
Compare
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: daa90ac5cc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
This was referenced Jun 14, 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
1 participant
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.
The Windows release workflow builds x64 and ARM64 in one matrix.
Each target's packaging job therefore waits for all six matrix cells,
even though it consumes artifacts from only the three cells for its
target.
In alpha.19, ARM64's builds completed at 01:40:38 UTC, but its
packaging job was not created until x64 completed at 01:51:42 UTC.
It then entered the x64 runner queue alongside x64 packaging.
https://github.com/openai/codex/actions/runs/27484551090
Invoke the reusable workflow once per target. Each invocation retains
the three bundle builds and starts symbol and package jobs as soon as
those target-specific builds finish.
ARM64 packaging took 6m05s on ARM in alpha.18 and 6m08s on x64 in
alpha.19. Keep packaging on each target's build runner. The 11-minute
ARM64 lead absorbs its runner queue and avoids consuming x64 capacity
alongside the critical x64 package.