Add repo-specific scale config files #127566
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/127566
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ✅ No FailuresAs of commit 5310478 with merge base 18a3f78 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@pytorchbot merge -f "lint passed. Other jobs are irrelevant" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: Approvers from one of the following sets are needed:
|
At least for now. This is how the pre-existing code expects per-repo level runners to be configured. A config in test-infra is expected for org-wide runners |
|
@pytorchbot merge -f "lint passed. Other jobs are irrelevant" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
…127578) Initial set of runners added in #127566 seem to be working. Expanding to include more machine types, especially GPU machines Pull Request resolved: #127578 Approved by: https://github.com/huydhn
Part of moving pytorch/pytorch CI infra to a Linux foundation run AWS account. For self-hosted runners that can run jobs from just a single repo, the runner scalers expect them to be stored in the repo itself. These scale-config files define how the linux foundation's self-hosted runners are configured. These will apply to runners that only are available to the pytorch/pytorch and pytorch/pytorch-canary repos Pull Request resolved: pytorch#127566 Approved by: https://github.com/zxiiro, https://github.com/huydhn, https://github.com/atalman
…ytorch#127578) Initial set of runners added in pytorch#127566 seem to be working. Expanding to include more machine types, especially GPU machines Pull Request resolved: pytorch#127578 Approved by: https://github.com/huydhn
Part of moving pytorch/pytorch CI infra to a Linux foundation run AWS account.
For self-hosted runners that can run jobs from just a single repo, the runner scalers expect them to be stored in the repo itself.
These scale-config files define how the linux foundation's self-hosted runners are configured. These will apply to runners that only are available to the pytorch/pytorch and pytorch/pytorch-canary repos