Move xla jobs to unstable workflow

[ZainRizvi]

Disables the job on PRs completely, so that we don't litter people's CI signals and use machines unnecessarily.

If you want to run these xla tests, add the ciflow/unstable label to your PR

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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.

✅ You can merge normally! (1 Unrelated Failure)

As of commit 77debb0 with merge base 1abff80 ():

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

• unstable / linux-jammy-py3_9-clang9-xla / test (xla, 1, 1, linux.12xlarge) (gh)
  sccache: error: couldn't connect to server

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

[ZainRizvi]

@pytorchbot merge

[pytorchmergebot]

This PR updates submodules third_party/composable_kernel

If those updates are intentional, please add "submodule" keyword to PR title/description.

[ZainRizvi]

@pytorchbot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

[pytorchmergebot]

Merge failed

Reason: 1 STARTUP failures reported, please check workflows syntax! unstable

Details for Dev Infra team

Raised by workflow job

[ZainRizvi]

@pytorchbot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

[pytorchmergebot]

Merge failed

Reason: 1 mandatory check(s) failed. The first few are:

• pull / linux-jammy-xpu-2025.1-py3.9 / build

Dig deeper by viewing the failures on hud

Details for Dev Infra team

Raised by workflow job

Failing merge rule: Core Maintainers

[ZainRizvi]

@pytorchbot merge -i "failures unrelated"

[pytorch-bot]

❌ 🤖 pytorchbot command failed:

@pytorchbot: error: unrecognized arguments: failures unrelated

usage: @pytorchbot [-h] {merge,revert,rebase,label,drci,cherry-pick} ...

Try @pytorchbot --help for more info.

[ZainRizvi]

@pytorchbot merge -i

[pytorchmergebot]

Merge started

Your change will be merged while ignoring the following 1 checks: unstable / linux-jammy-py3_9-clang9-xla / test (xla, 1, 1, linux.12xlarge)

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

[pgmoka]

@ZainRizvi One of the issues cited was pytorch/xla#9499. I believe pytorch/xla#9499 (comment) should resolve the issue related to JAX versioning.