Skip to content

Conversation

@atalman
Copy link
Contributor

@atalman atalman commented Jun 17, 2025

Rebase of Test: #153117

@pytorch-bot
Copy link

pytorch-bot bot commented Jun 17, 2025

🔗 Helpful Links

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

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

❌ 51 New Failures, 1 Cancelled Job

As of commit 1923ec2 with merge base ebab279 (image):

NEW FAILURES - The following jobs have failed:

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

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

@pytorch-bot pytorch-bot bot added ciflow/inductor ciflow/trunk Trigger trunk jobs on your pull request topic: not user facing topic category labels Jun 17, 2025
@atalman atalman added keep-going Don't stop on first failure, keep running tests until the end ciflow/rocm Trigger "default" config CI on ROCm ci-no-td Do not run TD on this PR ciflow/h100 labels Jun 17, 2025
@atalman atalman force-pushed the triton_pin_update branch from 948fed7 to 20d198c Compare June 17, 2025 16:19
@atalman atalman changed the title Triton 3.4.0 pin update [TEST] Triton 3.4.0 pin update Jun 17, 2025
@atalman
Copy link
Contributor Author

atalman commented Jun 20, 2025

@pytorchmergebot rebase -b main

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

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

@jataylo
Copy link
Collaborator

jataylo commented Jun 24, 2025

ROCm jobs are failing at this commit @atalman @davidberard98

Last testing we did was with triton-lang/triton@6d5fb9f which was passing on ROCm #155117 there seems to have been a regression in that week of difference.

What should we do here?

@davidberard98
Copy link
Contributor

@atalman @jataylo I think we can try the older commit on which ROCm was passing. As a bonus, it's possible this may skip the commit that is causing the persistent_tma test to fail. IIUC we don't have any other Triton commits that we need, aside from triton-lang/triton#7219 which we would have needed to cherry-pick anyway.

@jataylo
Copy link
Collaborator

jataylo commented Jun 25, 2025

Looks like @iupaikov-amd's PR #155117 which used the proposed commit 5389ed797016010543ef1c7b88efc50f7521cb4e passes ROCm CI.

Can we try a rebase here @atalman ?

@jataylo jataylo added ciflow/inductor-rocm Trigger "inductor" config CI on ROCm ciflow/rocm-mi300 Trigger "default" config CI on ROCm MI300 labels Jun 25, 2025
@eellison eellison removed their request for review July 16, 2025 15:01
@atalman atalman closed this Aug 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-no-td Do not run TD on this PR 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 topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants