Update triton xpu commit pin

[guangyey]

Stack from ghstack (oldest at bottom):

• -> Update triton xpu commit pin #137886
• [Reland] Fix tensor.data_ptr() representation overflow #135567

Motivation

Due to the code change of #135567, triton-xpu needs to fetch tensor.data_ptr() via uint64 instead of int64, refer to intel/intel-xpu-backend-for-triton#2192

Additional Context

triton commit comes from release branch: https://github.com/intel/intel-xpu-backend-for-triton/tree/release/3.2.0

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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! (2 Unrelated Failures)

As of commit bc428ce with merge base 9b89fa4 ():

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• xpu / linux-jammy-xpu-2025_0-py3.9 / test (default, 1, 4, linux.idc.xpu) (gh) (similar failure)
  ##[error]An error has occurred while creating the zip file for upload

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

• inductor / cuda12.1-py3.10-gcc9-sm86 / test (inductor_timm, 1, 2, linux.g5.4xlarge.nvidia.gpu) (gh) (#141703)
  convnext_base

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

[guangyey]

These failures are related with intel/intel-xpu-backend-for-triton#2488.

[guangyey]

@pytorchbot rebase

[pytorchmergebot]

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

[pytorchmergebot]

Successfully rebased gh/guangyey/76/orig onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/137886)

[guangyey]

@pytorchbot rebase

[pytorchmergebot]

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

[pytorchmergebot]

Successfully rebased gh/guangyey/76/orig onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/137886)

[chuanqi129]

The only one UT failure appeared in doctests, there is an issue to track it #141705

[atalman]

lgtm.

[EikanWang]

@pytorchbot merge -i

[pytorchmergebot]

Merge started

Your change will be merged while ignoring the following 2 checks: inductor / cuda12.1-py3.10-gcc9-sm86 / test (inductor_timm, 1, 2, linux.g5.4xlarge.nvidia.gpu), xpu / linux-jammy-xpu-2025_0-py3.9 / test (default, 1, 4, linux.idc.xpu)

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