Repository navigation
Allocate more CI runners to Windows with asymmetric sharding - #916
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
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.
Allocate one Linux shard and five Windows shards per supported Ruby version instead of three shards for both operating systems. This keeps 18 test jobs and full Ruby/OS coverage while assigning more of the available runners to the Windows bottleneck. Extend the shard-selector examples to cover five shards.
GitHub CI measurements:
All three candidate runs are faster than the fresh control. Final verification passes every test job, lint, coverage finalization, the required CI check, and external coverage statuses. Logs verify the complete 1,698-example suite on each of six Ruby/OS combinations (10,188 executions), with matching discovery identities across shards. Local shard-selector examples, RuboCop, and actionlint pass.
Coverage flags identify the Ruby/OS/shard index and shard count rather than global matrix position, so changing the shard layout does not compare partial coverage against unrelated old shards. Combined coverage remains unchanged at 92.408%.