Update triton xpu commit to support python 3.14 by chuanqi129 · Pull Request #160183 · pytorch/pytorch

chuanqi129 · 2025-08-08T10:01:28Z

Follow PR #159725

pytorch-bot · 2025-08-08T10:01:33Z

🔗 Helpful Links

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

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

As of commit 5715d40 with merge base 371eacb ():

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

pull / linux-jammy-py3.9-gcc11 / test (default, 4, 5, linux.2xlarge) (gh) (matched linux rule in flaky-rules.json)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
pull / linux-jammy-py3.9-gcc11 / test (distributed, 2, 2, linux.2xlarge) (gh) (detected as infra flaky with no log or failing log classifier)
xpu / linux-jammy-xpu-2025.1-py3.9 / test (default, 2, 6, linux.idc.xpu) (gh) (similar failure)
inductor/test_torchinductor_codegen_dynamic_shapes.py::DynamicShapesCodegenGPUTests::test_repeat_interleave_2_dynamic_shapes_xpu
xpu / linux-jammy-xpu-2025.1-py3.9 / test (default, 5, 6, linux.idc.xpu) (gh) (similar failure)
inductor/test_aot_inductor.py::AOTInductorTestABICompatibleGpu::test_copy_non_blocking_is_pinned_xpu

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

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

inductor / cuda12.8-py3.10-gcc9-sm86 / test (inductor_torchbench, 2, 2, linux.g5.4xlarge.nvidia.gpu) (gh) (trunk failure)
vision_maskrcnn

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

atalman

lgtm

atalman · 2025-08-12T14:00:47Z

@pytorchmergebot merge -f "triton, inductor and lint are green"

pytorchmergebot · 2025-08-12T14:02:18Z

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

clee2000 · 2025-08-12T15:27:20Z

@pytorchbot revert -m "I'm not sure how, but it seems to have broken inductor/test_extension_backend.py::ExtensionBackendTests::test_open_device_registration GH job link HUD commit link. Maybe because the docker build changed? nvm I think the disabled test json was not getting pulled. But also broke triton windows whl build GH job link HUD commit link. Note to self: not bad TD re the test" -c nosignal

pytorchmergebot · 2025-08-12T15:29:13Z

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

This reverts commit 7fbc228. Reverted #160183 on behalf of https://github.com/clee2000 due to I'm not sure how, but it seems to have broken inductor/test_extension_backend.py::ExtensionBackendTests::test_open_device_registration [GH job link](https://github.com/pytorch/pytorch/actions/runs/16911267995/job/47917091939) [HUD commit link](https://hud.pytorch.org/pytorch/pytorch/commit/7fbc22855c17741ae016992803b2e147a13aa22d). Maybe because the docker build changed? Note to self: not bad TD ([comment](#160183 (comment)))

pytorchmergebot · 2025-08-12T15:29:23Z

@chuanqi129 your PR has been successfully reverted.

Follow PR pytorch#159725 Pull Request resolved: pytorch#160183 Approved by: https://github.com/EikanWang, https://github.com/atalman

Follow PR #159725 Pull Request resolved: #160183 Approved by: https://github.com/EikanWang, https://github.com/atalman

This reverts commit 7fbc228. Reverted #160183 on behalf of https://github.com/clee2000 due to I'm not sure how, but it seems to have broken inductor/test_extension_backend.py::ExtensionBackendTests::test_open_device_registration [GH job link](https://github.com/pytorch/pytorch/actions/runs/16911267995/job/47917091939) [HUD commit link](https://hud.pytorch.org/pytorch/pytorch/commit/7fbc22855c17741ae016992803b2e147a13aa22d). Maybe because the docker build changed? Note to self: not bad TD ([comment](#160183 (comment)))

chuanqi129 · 2025-08-15T05:33:26Z

@pytorchbot merge

pytorchmergebot · 2025-08-15T05:35:13Z

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

Follow PR #159725 Pull Request resolved: #160183 Approved by: https://github.com/EikanWang, https://github.com/atalman

This reverts commit 7fbc228. Reverted #160183 on behalf of https://github.com/clee2000 due to I'm not sure how, but it seems to have broken inductor/test_extension_backend.py::ExtensionBackendTests::test_open_device_registration [GH job link](https://github.com/pytorch/pytorch/actions/runs/16911267995/job/47917091939) [HUD commit link](https://hud.pytorch.org/pytorch/pytorch/commit/7fbc22855c17741ae016992803b2e147a13aa22d). Maybe because the docker build changed? Note to self: not bad TD ([comment](#160183 (comment)))

Follow PR pytorch#159725 Pull Request resolved: pytorch#160183 Approved by: https://github.com/EikanWang, https://github.com/atalman

…)" This reverts commit 7fbc228. Reverted pytorch#160183 on behalf of https://github.com/clee2000 due to I'm not sure how, but it seems to have broken inductor/test_extension_backend.py::ExtensionBackendTests::test_open_device_registration [GH job link](https://github.com/pytorch/pytorch/actions/runs/16911267995/job/47917091939) [HUD commit link](https://hud.pytorch.org/pytorch/pytorch/commit/7fbc22855c17741ae016992803b2e147a13aa22d). Maybe because the docker build changed? Note to self: not bad TD ([comment](pytorch#160183 (comment)))

Follow PR pytorch#159725 Pull Request resolved: pytorch#160183 Approved by: https://github.com/EikanWang, https://github.com/atalman

…)" This reverts commit 7fbc228. Reverted pytorch#160183 on behalf of https://github.com/clee2000 due to I'm not sure how, but it seems to have broken inductor/test_extension_backend.py::ExtensionBackendTests::test_open_device_registration [GH job link](https://github.com/pytorch/pytorch/actions/runs/16911267995/job/47917091939) [HUD commit link](https://hud.pytorch.org/pytorch/pytorch/commit/7fbc22855c17741ae016992803b2e147a13aa22d). Maybe because the docker build changed? Note to self: not bad TD ([comment](pytorch#160183 (comment)))

Follow PR pytorch#159725 Pull Request resolved: pytorch#160183 Approved by: https://github.com/EikanWang, https://github.com/atalman

chuanqi129 requested a review from atalman August 8, 2025 10:01

chuanqi129 requested review from EikanWang and gujinghui as code owners August 8, 2025 10:01

chuanqi129 added topic: not user facing topic category ciflow/xpu Run XPU CI tasks labels Aug 8, 2025

pytorch-bot Bot added the ciflow/inductor label Aug 8, 2025

pytorchbot added the open source label Aug 8, 2025

anmyachev mentioned this pull request Aug 8, 2025

[NOT MERGE] just to see how rel/3.4 branch for PyTorch looks like intel/intel-xpu-backend-for-triton#4865

Closed

EikanWang approved these changes Aug 11, 2025

View reviewed changes

chuanqi129 added the ciflow/trunk Trigger trunk jobs on your pull request label Aug 11, 2025

atalman approved these changes Aug 12, 2025

View reviewed changes

pytorchmergebot added the merging label Aug 12, 2025

pytorchmergebot closed this in 7fbc228 Aug 12, 2025

pytorchmergebot added Merged and removed merging labels Aug 12, 2025

pytorchmergebot added Reverted ci-no-td Do not run TD on this PR labels Aug 12, 2025

pytorchmergebot reopened this Aug 12, 2025

chuanhaozhuge pushed a commit that referenced this pull request Aug 14, 2025

Update triton xpu commit to support python 3.14 (#160183)

294be9f

Follow PR #159725 Pull Request resolved: #160183 Approved by: https://github.com/EikanWang, https://github.com/atalman

Update triton xpu commit to support python 3.14

5715d40

chuanqi129 force-pushed the triton_xpu_py314 branch from a09c969 to 5715d40 Compare August 14, 2025 23:38

pytorchmergebot added the merging label Aug 15, 2025

pytorchmergebot closed this in 4cae9cf Aug 15, 2025

pytorchmergebot removed the merging label Aug 15, 2025

chuanhaozhuge pushed a commit that referenced this pull request Aug 18, 2025

Update triton xpu commit to support python 3.14 (#160183)

f3e1732

Follow PR #159725 Pull Request resolved: #160183 Approved by: https://github.com/EikanWang, https://github.com/atalman

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update triton xpu commit to support python 3.14#160183

Update triton xpu commit to support python 3.14#160183
chuanqi129 wants to merge 1 commit into
pytorch:mainfrom
chuanqi129:triton_xpu_py314

chuanqi129 commented Aug 8, 2025

Uh oh!

pytorch-bot Bot commented Aug 8, 2025 •

edited

Loading

Uh oh!

atalman left a comment

Uh oh!

atalman commented Aug 12, 2025

Uh oh!

pytorchmergebot commented Aug 12, 2025

Uh oh!

clee2000 commented Aug 12, 2025 •

edited

Loading

Uh oh!

pytorchmergebot commented Aug 12, 2025

Uh oh!

pytorchmergebot commented Aug 12, 2025

Uh oh!

chuanqi129 commented Aug 15, 2025

Uh oh!

pytorchmergebot commented Aug 15, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Conversation

chuanqi129 commented Aug 8, 2025

Uh oh!

pytorch-bot Bot commented Aug 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔗 Helpful Links

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

✅ You can merge normally! (5 Unrelated Failures)

Uh oh!

atalman left a comment

Choose a reason for hiding this comment

Uh oh!

atalman commented Aug 12, 2025

Uh oh!

pytorchmergebot commented Aug 12, 2025

Merge started

Uh oh!

clee2000 commented Aug 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pytorchmergebot commented Aug 12, 2025

Uh oh!

pytorchmergebot commented Aug 12, 2025

Uh oh!

chuanqi129 commented Aug 15, 2025

Uh oh!

pytorchmergebot commented Aug 15, 2025

Merge started

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

pytorch-bot Bot commented Aug 8, 2025 •

edited

Loading

clee2000 commented Aug 12, 2025 •

edited

Loading