Repository navigation
Run the v1 multi-rank CPU suite on pull requests #8944
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,10 +13,9 @@ name: cpu-torch-latest-v1-multirank | |
| # DS_MULTIRANK_ONLY drops single-rank tests, so a run spends its time on | ||
| # world_size 2-4 CPU tests. | ||
| # | ||
| # Trigger rollout: manual dispatch only for now. Starting as a required | ||
| # pull_request check would put an unvalidated ~1h suite in front of every PR; | ||
| # once this run is green across a few real PRs, add `pull_request:` back to the | ||
| # `on:` block and register the check with branch protection. | ||
| # Trigger rollout: manual dispatch validated the suite on master, so it now | ||
| # also runs on pull requests and in the merge queue; register the unit-tests | ||
| # check with branch protection to make it required. | ||
|
|
||
| on: | ||
| workflow_dispatch: | ||
|
|
@@ -49,6 +48,9 @@ on: | |
| required: false | ||
| default: 'main' | ||
| type: string | ||
| pull_request: | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
For a PR that changes Useful? React with 👍 / 👎. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
For a PR whose selected subset contains no retained multi-rank item—for example, a direct edit to Useful? React with 👍 / 👎. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
When a PR's target branch has advanced, Useful? React with 👍 / 👎. |
||
| merge_group: | ||
| branches: [ master ] | ||
|
|
||
| concurrency: | ||
| group: ${{ github.workflow }}-${{ github.ref }} | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once this pull-request job is made required, a failure in
check-pathsorcollect-tests(checkout, selector, validation, artifact upload, or runner failure) leavesneeds.collect-tests.result != 'success', so the condition at.github/workflows/cpu-torch-latest-v1-multirank.yml:122skipsunit-tests; skipped dependent jobs satisfy a required check, as the Modal workflow notes and guards against at.github/workflows/modal-torch-latest.yml:271-280, and the PR can merge without tests. Make the required job enter an explicit failing guard whenever collection was expected but failed, while retaining intentional path andmode=noneskips.Useful? React with 👍 / 👎.