DO NOT CLOSE IT / GitHub workflows / Access Rules #5132
Comments
|
atalman |
DanilBaibak
changed the title
pytorchmergebot
pushed a commit
to pytorch/pytorch
that referenced
this issue
May 10, 2024
This PR introduces a tool to dynamically switch between ARC runners and old runners without having to update the PR to the latest version. There is also a third option - use both runners at the same time (aka shadow deployment). In this case, failed workflows using ARC launchers will not block merge process. The GitHub issue is used to control access to ARC launchers - [Access Rules Issue](pytorch/test-infra#5132): * In the FIRST comment you can specify who will use the ARC runners: * Add a GitHub username to use ARC runners. * Add "*" at the beginning to switch ALL users to ARC runners. * Add "!" at the beginning to switch ALL users to old runners. * In the SECOND comment you can specify do we need to run ARC runners and old runners at the same time. * To use both runners, add a second comment with the word "both". * If we want to use only one type of runners, just remove the second comment. Pull Request resolved: #125680 Approved by: https://github.com/ZainRizvi
|
Should we close this? |
DanilBaibak
changed the title
|
No, pls don't close the issue. It will be used for dynamic rollout while we are migrating from our runners to the linux foundation runners. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the FIRST comment you can specify who will use the linux foundation (LF) runners:
The text was updated successfully, but these errors were encountered: