Skip to content

[ROCm][CI] Switch ROCm CI runner label from gfx942 to ecosystem.mi350 - #9587

Closed
akashveramd wants to merge 1 commit into
pytorch:mainfrom
akashveramd:av_mi350_label
Closed

akashveramd wants to merge 1 commit into
pytorch:mainfrom
akashveramd:av_mi350_label

Conversation

@akashveramd

@akashveramd akashveramd commented Aug 6, 2026

Copy link
Copy Markdown

This PR replaces gfx942 label with ecosystem.mi350 label.

cc @jeffdaily @jithunnair-amd

@pytorch-bot

pytorch-bot Bot commented Aug 6, 2026

Copy link
Copy Markdown

🔗 Helpful Links

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

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

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

@meta-cla meta-cla Bot added the cla signed label Aug 6, 2026
@NicolasHug

Copy link
Copy Markdown
Member

Thanks @akashveramd but I'll close this for the same reason as #9567

@jithunnair-amd

Copy link
Copy Markdown
Contributor

@NicolasHug Just want to reconfirm: while the rocjpeg functionality has been moved over to torchcodec, is there no value to be gained by having ROCm CI on torchvision? There's still other GPU code on torchvision to be tested, right? Especially since we release ROCm builds of torchvision wheels on download.pytorch.org...

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants