Skip to content

Merge from AMD - #992

Merged
arjunsuresh merged 6 commits into
mlcommons:devfrom
amd:dev
Jun 8, 2026
Merged

Merge from AMD#992
arjunsuresh merged 6 commits into
mlcommons:devfrom
amd:dev

Conversation

@amd-arsuresh

Copy link
Copy Markdown
Contributor

🧾 PR Checklist

  • Target branch is dev

📌 Note: PRs must be raised against dev. Do not commit directly to main.

📁 File Hygiene & Output Handling

  • No unintended files (e.g., logs, cache, temp files, pycache, output folders) are committed

📝 Comments & Communication

  • Proper inline comments are added to explain important or non-obvious changes
  • PR title and description clearly state what the PR does and why
  • Related issues (if any) are properly referenced (Fixes #, Related to #, etc.)

🛡️ Safety & Security

  • No secrets or credentials are committed
  • Paths, shell commands, and environment handling are safe and portable

@amd-arsuresh
amd-arsuresh requested a review from a team as a code owner June 8, 2026 15:15
@github-actions

github-actions Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

arjunsuresh and others added 5 commits June 8, 2026 20:51
Added SHA variation for install-gcc-src
… sysinfo

Two bugs prevented get-xpu-devices from ever being invoked:

1. get-mlperf-single-node-system-info/meta.yaml: dep enable_if_env guards
   referenced MLC_GPU_PLATFORM but the variations set MLC_ACCELERATOR_BACKEND,
   so the get,cuda-devices / get,rocm-devices / get,xpu-devices deps never
   fired. Updated all three guards to check MLC_ACCELERATOR_BACKEND.

2. get-mlperf-multi-node-system-info/customize.py: remote-run tag propagation
   only appended _cuda for CUDA; rocm and xpu backends had no equivalent case.
   Replaced the if/elif chain with a single membership check covering all three.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@arjunsuresh
arjunsuresh merged commit f579af1 into mlcommons:dev Jun 8, 2026
115 of 125 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 8, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants