Split macos-15-intel bundler tests into four shards#9575
Merged
Conversation
A single macos-15-intel runner took around 40 minutes. Reuse the Windows tag groups to fan the run out to four runners, keeping each under roughly ten minutes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
These groups now drive the macOS Intel split as well as Windows, so the "windows" naming no longer fits. Rename the module to Spec::Shards and the tags to shard_a..d. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Matches the shard_a..d tag names so the matrix variable reads consistently with what it selects. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adjusts Bundler CI sharding so the macos-15-intel regression run is split across four shard jobs (matching the existing Windows shard grouping), reducing per-job runtime while preserving the existing sharded test selection mechanism in the spec suite.
Changes:
- Rename/generalize the test file-to-tag mapping from Windows-specific groups to generic
shard_a–shard_dtags. - Update RSpec metadata/tag wiring to use
Spec::Shards::EXAMPLE_MAPPINGS. - Update the Bundler GitHub Actions workflow to run Windows and
macos-15-intelvia shard-tagged runs and add the 4-waymacos-15-intelmatrix entries.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
spec/support/shards.rb |
Renames Windows-specific tag groups to generic shard tags while keeping the same file-to-tag allocations. |
spec/spec_helper.rb |
Switches RSpec setup to load/include Spec::Shards and to derive shard metadata and warnings from shard tags. |
.github/workflows/bundler.yml |
Adds four macos-15-intel shard jobs and renames Windows “group” matrix entries to “shard”, running shard-tagged test subsets for both. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
What was the end-user or developer problem that led to this PR?
The
macos-15-intelrunner added in #9573 ran the full bundler suite in around 40 minutes, which is too long for regression coverage.What is your fix for the problem, implemented in this PR?
It now splits across four runners using the same example grouping that Windows already relies on, bringing each run down to roughly ten minutes.
Make sure the following tasks are checked