Deprecate MPS backend

[metascroy]

Differential Revision: D97825833

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 5 Unrelated Failures

As of commit fa4a507 with merge base 2309bfa ():

NEW FAILURES - The following jobs have failed:

• trunk / test-qnn-optimum-model (fp32, distilbert) / linux-job (gh)
  RuntimeError: Command docker exec -t f4c16d948056136487771590d0203d58f3c555b364b184caa8a1a47b0eeaf0ba /exec failed with exit code 92
• trunk / test-qnn-optimum-model (fp32, dit) / linux-job (gh)
  RuntimeError: Command docker exec -t 8037a895f66b502406e59f222d3e9844e6148c30878012af9261da48eb351ddb /exec failed with exit code 92

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

• pull / test-llama-runner-linux (bf16, custom, linux.2xlarge, executorch-ubuntu-22.04-clang12) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)
• pull / test-models-linux (resnet50, portable, linux.2xlarge) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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

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

• pull / unittest / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• trunk / unittest-release / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.

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

[meta-codesync]

@metascroy has exported this pull request. If you are a Meta employee, you can view the originating Diff in D97825833.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[meta-codesync]

@metascroy has imported this pull request. If you are a Meta employee, you can view this in D97825833.

[digantdesai]

Do we want to disable any high freq tests? we can keep them on slow freq or disable them in favor of just nighly runs.

[metascroy]

You mean lower the frequency of existing MPS tests due to planned deprecation?

If so, I'd rather leave them running. We shouldn't break MPS during the deprecation period.

[metascroy]

@pytorchbot cherry-pick --onto release/1.2 -c critical

[pytorchbot]

Cherry picking #18425

The cherry pick PR is at #18470 and it is recommended to link a critical cherry pick PR with an issue. The following tracker issues are updated:

• [v1.2.0] Release Schedule and Tracker #17016 (comment)

Details for Dev Infra team

Raised by workflow job