Skip to content

Add a reusable sharded nextest workflow - #5

Draft
zanieb wants to merge 4 commits into
mainfrom
zb/nextest-sharded-workflow-20260911
Draft

Add a reusable sharded nextest workflow#5
zanieb wants to merge 4 commits into
mainfrom
zb/nextest-sharded-workflow-20260911

Conversation

@zanieb

@zanieb zanieb commented Sep 11, 2026

Copy link
Copy Markdown
Member

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/nextest action for each partition. Projects keep their toolchain, cache, features, and filesystem fixtures in that local action; the shared nextest action 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants