Skip to content

fix: add H200, B200 and B300 to NUM_GPUS_OF_HARDWARE - #2585

Merged
yueming-yuan merged 2 commits into
mainfrom
add-h200-b300-num-gpus
Aug 17, 2026
Merged

fix: add H200, B200 and B300 to NUM_GPUS_OF_HARDWARE#2585
yueming-yuan merged 2 commits into
mainfrom
add-h200-b300-num-gpus

Conversation

@yueming-yuan

@yueming-yuan yueming-yuan commented Aug 17, 2026

Copy link
Copy Markdown
Collaborator

Running scripts/run_qwen3_30b_a3b.py --hardware B300 without an explicit --num-gpus-per-node fails with KeyError: 'B300' in ScriptArgs.__post_init__, because NUM_GPUS_OF_HARDWARE only lists H100/GB200/GB300/MI350X/MI355X. Same for H200 and B200.

Add H200, B200 and B300 (8 GPUs per node) so --hardware alone works on these machines.

Found while smoke-testing release/v0.1.0 nvfp4 training on a B300 devbox.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

Tip: disable this comment in your organization's Code Review settings.

@yueming-yuan yueming-yuan changed the title fix: add H200 and B300 to NUM_GPUS_OF_HARDWARE fix: add H200, B200 and B300 to NUM_GPUS_OF_HARDWARE Aug 17, 2026
@yueming-yuan
yueming-yuan merged commit e4152f6 into main Aug 17, 2026
24 checks passed
@yueming-yuan
yueming-yuan deleted the add-h200-b300-num-gpus branch August 17, 2026 23:18
github-actions Bot pushed a commit that referenced this pull request Aug 18, 2026
yueming-yuan added a commit that referenced this pull request Aug 24, 2026
Launchers hardcode a --hardware default, so running one on anything else
silently applies the wrong profile unless the flag is passed. detect_hardware()
resolves the node to a NUM_GPUS_OF_HARDWARE key: compute capability picks the
generation, the host CPU separates Grace from the x86 part carrying the same
die, and HBM capacity splits H100 from H200. It is a lookup at the point of use,
not at construction, so prepare steps keep running GPU-free; the snapshot
harness freezes it.

GENERATION_HARDWARE gains H200/B200/B300, and the table check now derives the
hardware it requires from every launcher's --hardware literal instead of a
hardcoded list that #2585 already drifted from.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants