[TESTING] [DO NOT MERGE] Updated triton commit pin #153548

iupaikov-amd · 2025-05-14T16:06:20Z

We would like to update triton version for 2.8 release and in order to do so we will need to compile a list of possible failures that can happen with triton ToT. This PR only exists to run CI jobs and gather data for this and will remain in draft form.

Commit taken as reference: triton-lang/triton@2ec711b

pytorch-bot · 2025-05-14T16:06:24Z

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

CUDA not found in NVIDIA runners

❌ 62 New Failures, 1 Cancelled Job, 2 Unrelated Failures

As of commit 4739b71 with merge base 86c6f71 ():

NEW FAILURES - The following jobs have failed:

Build manywheel docker images for s390x / build-docker-cpu-s390x (gh)
ValueError: SELinux policy is not managed or store cannot be accessed.
Build Triton wheels / Build Triton Wheel (3.10, aarch64, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.10, cuda, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.10, rocm, pytorch/manylinux2_28-builder:cpu) (gh)
ValueError: SELinux policy is not managed or store cannot be accessed.
Build Triton wheels / Build Triton Wheel (3.10, xpu, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.11, aarch64, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.11, cuda, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.11, rocm, pytorch/manylinux2_28-builder:cpu) (gh)
ValueError: SELinux policy is not managed or store cannot be accessed.
Build Triton wheels / Build Triton Wheel (3.11, xpu, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.12, aarch64, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.12, cuda, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.12, rocm, pytorch/manylinux2_28-builder:cpu) (gh)
ValueError: SELinux policy is not managed or store cannot be accessed.
Build Triton wheels / Build Triton Wheel (3.12, xpu, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.13, aarch64, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.13, cuda, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.13, rocm, pytorch/manylinux2_28-builder:cpu) (gh)
ValueError: SELinux policy is not managed or store cannot be accessed.
Build Triton wheels / Build Triton Wheel (3.13, xpu, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.13t, aarch64, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.13t, cuda, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.13t, rocm, pytorch/manylinux2_28-builder:cpu) (gh)
ValueError: SELinux policy is not managed or store cannot be accessed.
Build Triton wheels / Build Triton Wheel (3.13t, xpu, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.9, aarch64, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.9, cuda, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Wheel (3.9, rocm, pytorch/manylinux2_28-builder:cpu) (gh)
ValueError: SELinux policy is not managed or store cannot be accessed.
Build Triton wheels / Build Triton Wheel (3.9, xpu, pytorch/manylinux2_28-builder:cpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Windows Wheel (3.10, xpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Windows Wheel (3.11, xpu) (gh)
Build Triton wheels / Build Triton Windows Wheel (3.12, xpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Windows Wheel (3.13, xpu) (gh)
Process completed with exit code 1.
Build Triton wheels / Build Triton Windows Wheel (3.13t, xpu) (gh)
Build Triton wheels / Build Triton Windows Wheel (3.9, xpu) (gh)
Process completed with exit code 1.
docker-builds / docker-build (linux.12xlarge, pytorch-linux-focal-cuda11.8-cudnn9-py3-gcc9) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-focal-cuda12.4-cudnn9-py3-gcc9-inductor-benchmarks) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-focal-cuda12.4-cudnn9-py3.12-gcc9-inductor-benchmarks) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-focal-cuda12.4-cudnn9-py3.13-gcc9-inductor-benchmarks) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-focal-cuda12.6-cudnn9-py3-gcc9-inductor-benchmarks) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-focal-cuda12.6-cudnn9-py3.12-gcc9-inductor-benchmarks) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-focal-cuda12.6-cudnn9-py3.13-gcc9-inductor-benchmarks) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-focal-py3.11-clang10) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-focal-py3.9-clang10) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-jammy-cuda11.8-cudnn9-py3.9-clang12) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-jammy-py3.12-halide) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-jammy-py3.12-triton-cpu) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-jammy-py3.9-gcc11-inductor-benchmarks) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-jammy-py3.9-gcc11) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-jammy-rocm-n-1-py3) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-jammy-rocm-n-py3) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-jammy-xpu-2025.0-py3) (gh)
Final attempt failed. Child_process exited with error code 1
docker-builds / docker-build (linux.12xlarge, pytorch-linux-jammy-xpu-2025.1-py3) (gh)
Final attempt failed. Child_process exited with error code 1
Lint / lintrunner-noclang / linux-job (gh)
>>> Lint for .github/scripts/build_triton_wheel.py:
pull / cuda12.4-py3.10-gcc9-sm75 / build (gh)
Final attempt failed. Child_process exited with error code 1
pull / linux-focal-cpu-py3.10-gcc11-bazel-test / build-and-test (default, 1, 1, linux.4xlarge) (gh)
Final attempt failed. Child_process exited with error code 1
pull / linux-focal-cuda11.8-py3.10-gcc9 / build (gh)
Final attempt failed. Child_process exited with error code 1
pull / linux-focal-cuda12.6-py3.10-gcc11 / build (gh)
Final attempt failed. Child_process exited with error code 1
pull / linux-focal-cuda12.6-py3.10-gcc11-sm89 / build (gh)
Final attempt failed. Child_process exited with error code 1
pull / linux-focal-py3.9-clang10 / build (gh)
Final attempt failed. Child_process exited with error code 1
pull / linux-jammy-py3.9-gcc11 / build (gh)
Final attempt failed. Child_process exited with error code 1
pull / linux-jammy-py3.9-gcc11-mobile-lightweight-dispatch-build / build (gh)
Final attempt failed. Child_process exited with error code 1
pull / linux-jammy-py3.9-gcc11-no-ops / build (gh)
Final attempt failed. Child_process exited with error code 1
pull / linux-jammy-py3.9-gcc11-pch / build (gh)
Final attempt failed. Child_process exited with error code 1
pull / linux-jammy-rocm-py3.10 / build (gh)
Final attempt failed. Child_process exited with error code 1
pull / linux-jammy-xpu-2025.1-py3.9 / build (gh)
Final attempt failed. Child_process exited with error code 1

CANCELLED JOB - The following job was cancelled. Please retry:

pull / linux-jammy-cuda11.8-cudnn9-py3.9-clang12 / build (gh)
##[error]The operation was canceled.

UNSTABLE - The following jobs are marked as unstable, possibly due to flakiness on trunk:

docker-builds / docker-build (linux.12xlarge, pytorch-linux-focal-cuda12.6-cudnn9-py3-gcc11) (gh) (related job)
Final attempt failed. Child_process exited with error code 1
pull / unstable-linux-focal-cuda12.6-py3.10-gcc11-sm89-xfail / build (gh)
Final attempt failed. Child_process exited with error code 1

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

pytorch-bot · 2025-05-14T16:08:24Z

To add the ciflow label ciflow/inductor please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

pytorch-bot · 2025-05-14T16:08:24Z

To add the ciflow label ciflow/inductor-rocm please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

pytorch-bot · 2025-05-14T16:08:25Z

To add the ciflow label ciflow/rocm-mi300 please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

pytorch-bot · 2025-05-14T16:08:25Z

To add the ciflow label ciflow/rocm please first approve the workflows that are awaiting approval (scroll to the bottom of this page).

This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows.

jithunnair-amd · 2025-05-16T19:55:46Z

@pytorchbot rebase

pytorchmergebot · 2025-05-16T19:57:19Z

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

pytorchmergebot · 2025-05-16T19:57:23Z

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

pytorch-bot bot added the topic: not user facing topic category label May 14, 2025

jataylo added ciflow/inductor ciflow/rocm Trigger "default" config CI on ROCm ciflow/inductor-rocm Trigger "inductor" config CI on ROCm ciflow/rocm-mi300 Trigger "default" config CI on ROCm MI300 labels May 14, 2025

pytorch-bot bot removed ciflow/inductor ciflow/inductor-rocm Trigger "inductor" config CI on ROCm ciflow/rocm-mi300 Trigger "default" config CI on ROCm MI300 ciflow/rocm Trigger "default" config CI on ROCm labels May 14, 2025

jataylo added ciflow/inductor ciflow/rocm Trigger "default" config CI on ROCm ciflow/inductor-rocm Trigger "inductor" config CI on ROCm ciflow/rocm-mi300 Trigger "default" config CI on ROCm MI300 labels May 14, 2025

jataylo changed the title ~~Updated triton commit pin~~ [TESTING] [DO NOT MERGE] Updated triton commit pin May 14, 2025

pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label May 14, 2025

pytorchbot added the open source label May 14, 2025

pytorch-bot bot removed ciflow/trunk Trigger trunk jobs on your pull request ciflow/inductor ciflow/rocm Trigger "default" config CI on ROCm ciflow/inductor-rocm Trigger "inductor" config CI on ROCm ciflow/rocm-mi300 Trigger "default" config CI on ROCm MI300 labels May 15, 2025

iupaikov-amd added 2 commits May 16, 2025 19:57

Updated triton commit pin

9af6c05

Adjusted triton installation to new folder structure

a72694a

Adjusted triton wheel installation to new folder structure

4739b71

pytorchmergebot force-pushed the iupaikov_triton_pin_update_upstream branch from 89e00c0 to 4739b71 Compare May 16, 2025 19:57

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[TESTING] [DO NOT MERGE] Updated triton commit pin #153548

[TESTING] [DO NOT MERGE] Updated triton commit pin #153548

[TESTING] [DO NOT MERGE] Updated triton commit pin #153548

Are you sure you want to change the base?

[TESTING] [DO NOT MERGE] Updated triton commit pin #153548

Conversation

🔗 Helpful Links

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

❗ 1 Active SEVs

❌ 62 New Failures, 1 Cancelled Job, 2 Unrelated Failures