Use Xcode 26 for benchmarks - #308
Merged
Merged
Conversation
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.
Summary
macos-15runner tomacos-26DEVELOPER_DIRto Xcode 26.6/Applications/Xcode_26.6.appbefore running benchmarksWhy
Benchmark runs should use the current Xcode 26 toolchain while keeping the compiler version explicit and repeatable. The GitHub
macos-26runner image includes Xcode 26.6 at the pinned path.Runner image reference: https://github.com/actions/runner-images/blob/main/images/macos/macos-26-arm64-Readme.md
Impact
Both candidate and baseline measurements continue to run in the same job and therefore use the same macOS runner and Xcode 26.6 toolchain.
Validation
.github/workflows/benchmark.ymlas YAMLbash -n scripts/benchmark.shDEVELOPER_DIR, andxcode-selectpath consistently target macOS/Xcode 26macos-15references remaingit diff --checkThe workflow still needs an end-to-end run on GitHub Actions.