feat(ci): run heavy tests only if PR is labeled with ready#11263
Closed
muXxer wants to merge 9 commits into
Closed
feat(ci): run heavy tests only if PR is labeled with ready#11263muXxer wants to merge 9 commits into
ready#11263muXxer wants to merge 9 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 5 Skipped Deployments
|
7dab1e7 to
46a885f
Compare
…"ready"; not running light tests on labeling, but still running couple of them required for heavy tests; checking SHA before running heavy tests to not run them twice if we got already success
added 2 commits
May 12, 2026 15:05
added 2 commits
May 12, 2026 17:24
…o ready-for-review" This reverts commit 1237f63.
6 tasks
Contributor
Author
|
Superseeded by #11540 |
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.
Description of change
To reduce the load on our CI runners, we will run heavy tests like
rust-tests,rust-simtests,split-cluster,split-cluster-sync-checkore2e(turbo-hierarchy.yml) only if a PR is marked withreadylabel.What changed
hierarchy.yml:split-clusterandsplit-cluster-sync-checkjobs now require the "ready" label on PRsturbo_hierarchy.yml:e2ejob now requires the "ready" label on PRs_rust_tests.yml:rust-tests,rust-simtestsjobs now require the "ready" label on PRsHow it works
Links to any relevant issues
#11253
How the change has been tested