Move Bazel Windows jobs onto codex-runners#24952
Merged
Merged
Conversation
597ea79 to
17eb77f
Compare
17eb77f to
7e69314
Compare
bolinfest
approved these changes
May 28, 2026
Collaborator
bolinfest
left a comment
There was a problem hiding this comment.
Thanks so much! Not sure how we missed this...
Collaborator
Author
|
Seems like its pretty easy during review to miss to me, and it maybe wouldn't have been apparent as affecting the long pole until the recent builder sharding changes? 🤷 |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 codex-windows runner group should be much faster than the default GHA runners. Since bazel jobs on windows are frequently the long pole for PRs checks, this will hopefully get people landing a bit faster.