Skip to content

Conversation

@iupaikov-amd
Copy link
Collaborator

@iupaikov-amd iupaikov-amd commented Jun 4, 2025

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@76b6977

@pytorch-bot
Copy link

pytorch-bot bot commented Jun 4, 2025

🔗 Helpful Links

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

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

❌ 50 New Failures, 8 Cancelled Jobs, 2 Unrelated Failures

As of commit e0c253a with merge base d9577df (image):

NEW FAILURES - The following jobs have failed:

CANCELLED JOBS - The following jobs were cancelled. Please retry:

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

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 Jun 4, 2025
@iupaikov-amd
Copy link
Collaborator Author

@pytorchbot rebase

@iupaikov-amd iupaikov-amd changed the title Updated triton commit pin [TESTING] [DO NOT MERGE] Updated triton commit pin Jun 4, 2025
@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

Tried to rebase and push PR #155117, but it was already up to date. Try rebasing against main by issuing:
@pytorchbot rebase -b main

@jataylo jataylo added 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 keep-going Don't stop on first failure, keep running tests until the end labels Jun 4, 2025
@iupaikov-amd
Copy link
Collaborator Author

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot pytorchmergebot force-pushed the iupaikov_triton_pin_update_upstream3 branch from 33c1a3b to fca5226 Compare June 6, 2025 09:04
@pytorch-bot 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 Jun 6, 2025
@xinyazhang
Copy link
Collaborator

@pytorchbot label "ciflow/inductor" "ciflow/inductor-rocm" "ciflow/rocm" "ciflow/rocm-mi300" "ciflow/trunk" "keep-going"

@pytorch-bot
Copy link

pytorch-bot bot commented Jun 6, 2025

To add these label(s) (ciflow/inductor, ciflow/inductor-rocm, ciflow/rocm, ciflow/rocm-mi300, ciflow/trunk) to the PR, 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.

@jeffdaily jeffdaily added 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 labels Jun 6, 2025
@pytorchmergebot pytorchmergebot force-pushed the iupaikov_triton_pin_update_upstream3 branch from 11da0d1 to 5169caf Compare June 24, 2025 16:20
@iupaikov-amd iupaikov-amd added 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 Jun 24, 2025
@pytorch-bot 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 Jun 25, 2025
@iupaikov-amd
Copy link
Collaborator Author

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot pytorchmergebot force-pushed the iupaikov_triton_pin_update_upstream3 branch from 6f3c666 to e0c253a Compare June 25, 2025 13:40
@iupaikov-amd iupaikov-amd added 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 Jun 25, 2025
@iupaikov-amd
Copy link
Collaborator Author

Closing since triton update was complete.

@iupaikov-amd iupaikov-amd deleted the iupaikov_triton_pin_update_upstream3 branch November 3, 2025 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/h100 ciflow/inductor ciflow/inductor-rocm Trigger "inductor" config CI on ROCm ciflow/rocm Trigger "default" config CI on ROCm ciflow/rocm-mi300 Trigger "default" config CI on ROCm MI300 ciflow/trunk Trigger trunk jobs on your pull request keep-going Don't stop on first failure, keep running tests until the end open source topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants