Skip to content

Re-enable triton XPU Python 3.15 Linux build#185094

Closed
chuanqi129 wants to merge 1 commit into
pytorch:mainfrom
chuanqi129:enable-triton-xpu-py315
Closed

Re-enable triton XPU Python 3.15 Linux build#185094
chuanqi129 wants to merge 1 commit into
pytorch:mainfrom
chuanqi129:enable-triton-xpu-py315

Conversation

@chuanqi129

@chuanqi129 chuanqi129 commented May 25, 2026

Copy link
Copy Markdown
Collaborator

Summary

Re-enable XPU triton wheel builds and manywheel builds for Python 3.15/3.15t on Linux.
fixes #184901

This reverts the XPU-specific exclusions added in #184829 and #184906.

Changes

  • .github/workflows/build-triton-wheel.yml: remove exclude block for xpu + 3.15/3.15t
  • .github/scripts/generate_binary_build_matrix.py: remove XPU 3.15 skip block
  • Regenerated generated-linux-binary-manywheel-nightly.yml to re-add manywheel-py3_15-xpu / manywheel-py3_15t-xpu entries

Test Plan

CI will validate via build-triton-wheel.yml and manywheel nightly workflows.

@chuanqi129 chuanqi129 requested a review from a team as a code owner May 25, 2026 02:07
@pytorch-bot

pytorch-bot Bot commented May 25, 2026

Copy link
Copy Markdown

🔗 Helpful Links

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

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

❌ 1 New Failure, 1 Unrelated Failure

As of commit 61ef4fd with merge base bb93923 (image):

NEW FAILURE - The following job has failed:

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

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

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 May 25, 2026
@chuanqi129 chuanqi129 requested a review from atalman May 25, 2026 02:49
@chuanqi129

Copy link
Copy Markdown
Collaborator Author

@pytorchbot merge

@pytorch-bot pytorch-bot Bot added the ciflow/trunk Trigger trunk jobs on your pull request label May 26, 2026
@pytorchmergebot

Copy link
Copy Markdown
Collaborator

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

Copy link
Copy Markdown
Collaborator

Merge failed

Reason: 1 jobs have failed, first few of them are: trunk / linux-jammy-rocm-py3.10-mi355 / test (default, 6, 10, linux.rocm.gpu.gfx950.1)

Details for Dev Infra team Raised by workflow job

@chuanqi129

Copy link
Copy Markdown
Collaborator Author

@pytorchbot merge -i

@pytorchmergebot

Copy link
Copy Markdown
Collaborator

Merge started

Your change will be merged while ignoring the following 23 checks: trunk / linux-jammy-aarch64-py3.10 / test (default, 4, 5, linux.arm64.m7g.4xlarge), trunk / linux-jammy-aarch64-py3.10 / test (default, 2, 5, linux.arm64.m7g.4xlarge), trunk / linux-jammy-aarch64-py3.10 / test-osdc (default, 5, 5, mt-l-arm64g3-16-62), trunk / linux-jammy-aarch64-py3.10 / test-osdc (default, 2, 5, mt-l-arm64g3-16-62), trunk / linux-jammy-rocm-py3.10-mi355 / test (default, 4, 10, linux.rocm.gpu.gfx950.1), trunk / linux-jammy-rocm-py3.10-mi355 / test (default, 10, 10, linux.rocm.gpu.gfx950.1), trunk / linux-jammy-rocm-py3.10-mi355 / test (distributed, 4, 4, linux.rocm.gpu.gfx950.2), trunk / linux-jammy-rocm-py3.10-mi355 / test (default, 6, 10, linux.rocm.gpu.gfx950.1), trunk / linux-jammy-rocm-py3.10-mi355 / test (default, 1, 10, linux.rocm.gpu.gfx950.1), trunk / linux-jammy-rocm-py3.10-mi355 / test (default, 2, 10, linux.rocm.gpu.gfx950.1), trunk / linux-jammy-rocm-py3.10-mi355 / test (distributed, 3, 4, linux.rocm.gpu.gfx950.2), trunk / linux-jammy-rocm-py3.10-mi355 / test (default, 3, 10, linux.rocm.gpu.gfx950.1), trunk / macos-py3-arm64 / test (default, 1, 3, macos-m1-stable), trunk / win-vs2022-cpu-py3 / test (default, 3, 4, windows.4xlarge.nonephemeral), trunk / win-vs2022-cpu-py3 / test (default, 4, 4, windows.4xlarge.nonephemeral), trunk / linux-jammy-cuda13.0-py3.10-gcc11 / test-osdc (default, 2, 5, mt-l-x86aavx2-29-113-l4), trunk / linux-jammy-cuda13.0-py3.10-gcc11 / test (default, 3, 5, linux.g6.4xlarge.experimental.nvidia.gpu), trunk / linux-jammy-cuda13.0-py3.10-gcc11 / test-osdc (distributed, 2, 3, mt-l-x86iavx512-45-172-t4-4), trunk / linux-jammy-cuda13.0-py3.10-gcc11 / test (distributed, 3, 3, linux.g4dn.12xlarge.nvidia.gpu), trunk / linux-jammy-cuda13.0-py3.10-gcc11 / test (default, 4, 5, linux.g6.4xlarge.experimental.nvidia.gpu), trunk / linux-jammy-cuda13.0-py3.10-gcc11 / test-osdc (distributed, 1, 3, mt-l-x86iavx512-45-172-t4-4), trunk / linux-jammy-cuda13.0-py3.10-gcc11 / test (distributed, 2, 3, linux.g4dn.12xlarge.nvidia.gpu), trunk / linux-jammy-cuda13.0-py3.10-gcc11 / test-osdc (default, 5, 5, mt-l-x86aavx2-29-113-l4)

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

@chuanqi129

Copy link
Copy Markdown
Collaborator Author

@pytorchbot rebase

@pytorchmergebot

Copy link
Copy Markdown
Collaborator

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

@pytorchmergebot

Copy link
Copy Markdown
Collaborator

Successfully rebased enable-triton-xpu-py315 onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout enable-triton-xpu-py315 && git pull --rebase)

@pytorchmergebot pytorchmergebot force-pushed the enable-triton-xpu-py315 branch from 4b71783 to 45fe96f Compare May 27, 2026 05:26
@chuanqi129

Copy link
Copy Markdown
Collaborator Author

@pytorchbot merge

@pytorchmergebot

Copy link
Copy Markdown
Collaborator

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

Copy link
Copy Markdown
Collaborator

Merge failed

Reason: 1 jobs have failed, first few of them are: Build Official Docker Images / build (cpu, runtime, linux/arm64)

Details for Dev Infra team Raised by workflow job

The XPU triton 3.15 wheel build issue (tracked in pytorch#184901) has been fixed.
Remove the exclusion added in pytorch#184829 and the manywheel skip added in pytorch#184906
so that XPU Python 3.15/3.15t builds run again.

Changes:
- .github/workflows/build-triton-wheel.yml: remove exclude block for xpu+3.15/3.15t
- .github/scripts/generate_binary_build_matrix.py: remove XPU 3.15 skip
- Regenerated generated-linux-binary-manywheel-nightly.yml

Test Plan: CI will validate via build-triton-wheel.yml and manywheel nightly.

Authored by Claude.
@chuanqi129 chuanqi129 force-pushed the enable-triton-xpu-py315 branch from 45fe96f to 61ef4fd Compare June 2, 2026 03:17
@chuanqi129

Copy link
Copy Markdown
Collaborator Author

@pytorchbot merge

@pytorchmergebot

Copy link
Copy Markdown
Collaborator

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

Copy link
Copy Markdown
Collaborator

Merge failed

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

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@chuanqi129

Copy link
Copy Markdown
Collaborator Author

@pytorchbot merge -i

@pytorchmergebot

Copy link
Copy Markdown
Collaborator

Merge started

Your change will be merged while ignoring the following 1 checks: pull / linux-jammy-py3.10-clang18 / test-osdc (crossref, 2, 2, mt-l-x86iavx512-8-64)

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk Trigger trunk jobs on your pull request Merged open source topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

XPU: Triton wheel builds for Python 3.15 are currently broken; skipped in build-triton-wheel.yml

5 participants