Enable dynamic rollout for pull workflow

[ZainRizvi]

Enables dynamic migration of jobs to the LF AWS account for the pull workflow. For now, it leaves out a few jobs that need a bit more testing: Namely Windows and Android runners.

The new runners are only given to people specified in this issue:
pytorch/test-infra#5132

Note: The non-pull jobs updated are the ones that have are synced to jobs in pull.yml (via sync-tag) and thus have to be updated whenever their corresponding pull.yml jobs are edited

Based on #128597

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/129243

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure, 2 Unrelated Failures

As of commit bf7f6c7 with merge base 920ebcc ():

NEW FAILURE - The following job has failed:

• pull / linux-jammy-py3.8-gcc11 / test (distributed, 1, 2, linux.2xlarge) (gh)
  Process completed with exit code 1.

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• trunk / macos-py3-arm64-mps / test (mps, 1, 1, macos-m1-13) (gh) (similar failure)
  test_mps.py::TestMPS::test_mps_allocator_module
• trunk / macos-py3-arm64-mps / test (mps, 1, 1, macos-m1-14) (gh) (similar failure)
  test_mps.py::TestMPS::test_mps_allocator_module

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[ZainRizvi]

@pytorchmergebot rebase

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[pytorchmergebot]

Successfully rebased zainr/ali-dynamic-rollout onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout zainr/ali-dynamic-rollout && git pull --rebase)

[huydhn]

Confirmed with @ZainRizvi that this would work without the need to do a rebase on people PR

[ZainRizvi]

@pytorchmergebot merge -i

[pytorchmergebot]

Merge started

Your change will be merged while ignoring the following 3 checks: pull / linux-jammy-py3.8-gcc11 / test (distributed, 1, 2, linux.2xlarge), trunk / macos-py3-arm64-mps / test (mps, 1, 1, macos-m1-13), trunk / macos-py3-arm64-mps / test (mps, 1, 1, macos-m1-14)

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[malfet]

Feels a bit weird to run _runner-determinator on linux-4xlarge, while lots of the jobs it's gating will be running on linux-2xlarge