chore(ci): add snap test sharding with --shard=X/Y support#1189
Merged
chore(ci): add snap test sharding with --shard=X/Y support#1189
Conversation
✅ Deploy Preview for viteplus-preview canceled.
|
Member
Author
How to use the Graphite Merge QueueAdd the label auto-merge to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| - os: namespace-profile-linux-x64-default | ||
| target: x86_64-unknown-linux-gnu | ||
| shard: 3 | ||
| shardTotal: 3 |
Check warning
Code scanning / zizmor
detects commit SHAs that don't match their version comment tags Warning
| target: x86_64-unknown-linux-gnu | ||
| shard: 2 | ||
| shardTotal: 3 | ||
| - os: namespace-profile-linux-x64-default |
Check notice
Code scanning / zizmor
credential persistence through GitHub Actions artifacts Note
Add Vitest-style --shard option to the snap test runner to split tests across multiple CI runners. The new cli-snap-test job runs 3 shards per OS (9 total matrix entries), reducing snap test wall-clock time by ~65%. The cli-e2e-test job now runs only unit tests, while snap tests are handled exclusively by the sharded cli-snap-test job.
The `pnpm script -- --shard=1/3` syntax passes `--` through to the script, causing parseArgs to treat `--shard` as a positional (filter) instead of an option. Use `pnpm -F ./packages/cli` to run scripts directly, which passes args without the `--` separator.
Tests using npm global operations (link, outdated -g, unlink) fail with ENOENT when sharded because the NPM_CONFIG_PREFIX directory was only implicitly created by whichever test ran `npm install -g` first. With sharding, that test may be in a different shard.
npm expects a `lib/` subdirectory inside NPM_CONFIG_PREFIX for global operations like link and outdated -g.
fengmk2
force-pushed
the
snap-test-sharding
branch
from
60903f6 to
2ddac25
Compare
branchseer
approved these changes
Mar 30, 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
3 participants
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.
Add Vitest-style --shard option to the snap test runner to split tests
across multiple CI runners. The new cli-snap-test job runs 3 shards per
OS (9 total matrix entries), reducing snap test wall-clock time by ~65%.
The cli-e2e-test job now runs only unit tests, while snap tests are
handled exclusively by the sharded cli-snap-test job.