Hardware support: MI325 / MI300 validation + CI
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 4
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 28
Description
From the 2026 Q3 roadmap.
Today: Validated on MI355X only.
Goal: Validate + CI on MI325 / MI300.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing MI355X validation workflow and CI entry points, then compare their hardware assumptions with MI325 and MI300. Done means both GPU families are validated and covered by CI, but the issue does not identify files, commands, or expected test results, so project-specific guidance is needed first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100