Add a reusable sharded nextest workflow - #5
Draft
zanieb wants to merge 4 commits into
Draft
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.
Centralize nextest shard planning, invocation, and artifact collection. The reusable workflow accepts a runner and numeric shard count, then invokes the caller's
.github/actions/nextestaction for each partition. Projects keep their toolchain, cache, features, and filesystem fixtures in that local action; the sharednextestaction owns hash partitioning, pending snapshots, JUnit results, and single-shard artifact naming.This keeps runner allocation separate from project-specific test setup and makes shard counts independently configurable on Linux, macOS, and Windows. Empty hash partitions succeed, while an unsharded run retains nextest's empty-suite policy. The uv integration is in astral-sh/uv-dev#1440.