Skip to content

[release/2.10] - Update triton commit and update logic to build from branch instead of triton.txt#3268

Open
jataylo wants to merge 2 commits into
ROCm:release/2.10from
jataylo:triton-internal-2.10
Open

[release/2.10] - Update triton commit and update logic to build from branch instead of triton.txt#3268
jataylo wants to merge 2 commits into
ROCm:release/2.10from
jataylo:triton-internal-2.10

Conversation

@jataylo
Copy link
Copy Markdown
Collaborator

@jataylo jataylo commented Jun 2, 2026

Update triton.txt for visibility but stop building from the txt file instead always use tip of branch

jataylo and others added 2 commits June 2, 2026 05:37
Update the Triton pin to the tip of ROCm release/internal/3.6.x and route
non-XPU Triton wheel builds through the ROCm fork.

Co-authored-by: Cursor <cursoragent@cursor.com>
Use release/internal/3.7.x for non-XPU Triton source builds in Docker and
wheel CI instead of checking out the triton.txt commit.

Co-authored-by: Cursor <cursoragent@cursor.com>
@rocm-repo-management-api
Copy link
Copy Markdown

rocm-repo-management-api Bot commented Jun 2, 2026

Jenkins build for fab61a27ee97d3ad76225bd2c667e756b5954984 commit finished as FAILURE
Links: Pipeline Overview / Build artifacts / Test Results

@ethanwee1
Copy link
Copy Markdown

@jataylo can you trigger pytorch builds here https://github.com/ROCm/TheRock/actions/workflows/build_portable_linux_pytorch_wheels.yml and link them in the PR description? That would ensure that theRock doesn't get affected by this change.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants