Use the shared sharded nextest workflow - #1440
Draft
zaniebot wants to merge 4 commits into
Draft
Conversation
astral-automations-bot
Bot
added
internal
zaniebot
added
risk:3
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
1 participant
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.
Move nextest runner allocation and artifact handling into the shared workflow from astral-sh/github-actions#5.
test.ymlselects the runner, timeout, cache policy, and shard count; uv-specific toolchains, Cargo features, Dev Drive, keychain, and filesystem fixtures remain in local platform actions. Explicit Unix Rust-cache keys keep the cache identity independent of the reusable workflow's job name.Linux defaults to one shard and Windows to three. macOS uses one complete test run on
mainand two shards when the existing CI plan enables it elsewhere, so opted-in pull requests can trade additional runner capacity for lower latency without increasing the normalmainrunner count. The aggregate required check still waits for the complete test workflow.