KEMBAR78
Remove explicit Amz2023 reference from jobs by ZainRizvi · Pull Request #134355 · pytorch/pytorch · GitHub
Skip to content

Conversation

@ZainRizvi
Copy link
Contributor

@ZainRizvi ZainRizvi commented Aug 23, 2024

Changes jobs to go back to using the default AMI.

Note: This is only a cleanup PR. It does NOT introduce any behavior changes in CI

Now that the default variant uses the Amazon 2023 AMI and has been shown to be stable for a week, it's time to remove the explicit amz2023 references and go back to using the default variant.

After a week or two, when this is rolled out to most people, we can remove the variants from scale config as well.

@ZainRizvi ZainRizvi requested a review from a team as a code owner August 23, 2024 18:42
@pytorch-bot
Copy link

pytorch-bot bot commented Aug 23, 2024

🔗 Helpful Links

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

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

❌ 27 New Failures, 102 Unrelated Failures

As of commit d1fb2ad with merge base 79b7fff (image):

NEW FAILURES - The following jobs have failed:

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

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

UNSTABLE - The following jobs failed but were likely due to flakiness present on trunk and has been marked as unstable:

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

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Aug 23, 2024
@ZainRizvi ZainRizvi force-pushed the zainr/remove-explicit-amz2023 branch from 8b4c8de to 66ec03d Compare August 23, 2024 18:47
@kit1980
Copy link
Contributor

kit1980 commented Aug 23, 2024

cc @atalman as we see issues in the release branch possibly related to Amz2023

@ZainRizvi ZainRizvi added ciflow/binaries Trigger all binary build and upload jobs on the PR ciflow/trunk Trigger trunk jobs on your pull request ciflow/slow ciflow/periodic Trigger jobs ran periodically on master (periodic.yml) on the PR ciflow/nightly Trigger all jobs we run nightly (nightly.yml) labels Aug 23, 2024
@ZainRizvi ZainRizvi force-pushed the zainr/remove-explicit-amz2023 branch from 66ec03d to d1fb2ad Compare August 26, 2024 23:28
@ZainRizvi
Copy link
Contributor Author

@pytorchbot merge -f "lint passed. Other failures are irrelevant"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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

Chao1Han pushed a commit to Chao1Han/pytorch that referenced this pull request Sep 20, 2024
Changes jobs to go back to using the default AMI.

Note: This is only a cleanup PR. It does NOT introduce any behavior changes in CI

Now that the default variant uses the Amazon 2023 AMI and has been shown to be stable for a week, it's time to remove the explicit amz2023 references and go back to using the default variant.

After a week or two, when this is rolled out to most people, we can remove the variants from scale config as well.
Pull Request resolved: pytorch#134355
Approved by: https://github.com/jeanschmidt
pytorchmergebot pushed a commit that referenced this pull request Sep 25, 2024
Validated no jobs use the amz2023 runner variant anymore ([proof](https://github.com/search?type=code&q=org%3Apytorch+%2F%5Cbamz2023%5Cb%2F+&p=1)) so removing all references to it

Explicit references to the amz2023 runner type variants were removed in the following PRs:
- pytorch/ignite#3285
- pytorch/ao#887
- meta-pytorch/fbscribelogger#1
- #134355

Pull Request resolved: #136540
Approved by: https://github.com/huydhn, https://github.com/malfet
BoyuanFeng pushed a commit to BoyuanFeng/pytorch that referenced this pull request Sep 25, 2024
Validated no jobs use the amz2023 runner variant anymore ([proof](https://github.com/search?type=code&q=org%3Apytorch+%2F%5Cbamz2023%5Cb%2F+&p=1)) so removing all references to it

Explicit references to the amz2023 runner type variants were removed in the following PRs:
- pytorch/ignite#3285
- pytorch/ao#887
- meta-pytorch/fbscribelogger#1
- pytorch#134355

Pull Request resolved: pytorch#136540
Approved by: https://github.com/huydhn, https://github.com/malfet
@github-actions github-actions bot deleted the zainr/remove-explicit-amz2023 branch October 2, 2024 02:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/binaries Trigger all binary build and upload jobs on the PR ciflow/nightly Trigger all jobs we run nightly (nightly.yml) ciflow/periodic Trigger jobs ran periodically on master (periodic.yml) on the PR ciflow/slow ciflow/trunk Trigger trunk jobs on your pull request Merged topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants