test: validate MI300 runtime selection and placement - #1045
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughAdds unit tests covering ROCm selection from KFD evidence and capacity-weighted split planning for an MI300X compared with a smaller accelerator. ChangesROCm runtime selection
Resource-aware split planning
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@crates/mesh-llm-hardware-profile/src/lib.rs`:
- Around line 719-721: Replace the EnvVarGuard-based environment mutation in the
ROCm detection tests with a pure helper that accepts the ROCm architecture
values directly. Update detect_rocm_profile_with_arches and the related tests to
reuse this helper, including the cases currently using EnvVarGuard, while
preserving each test’s expected profile behavior.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: a65ff85a-72de-4f0a-bdee-6b5300501414
📒 Files selected for processing (2)
crates/mesh-llm-hardware-profile/src/lib.rscrates/mesh-llm-host-runtime/src/runtime/split_planning.rs
e5278c8 to
3f4aa50
Compare
3f4aa50 to
5924fe1
Compare
…ngram * origin/main: Add GLM DSA correctness trace reporting (#1033) Add GLM DSA package contract validation (#1032) Add direct quant layer package tooling (#1031) Lock split topology placement (#1050) fix nightly stability Qwen thinking ui(data-mode): migrate legacy harness storage to v2 (#1040) fix: Windows Vulkan runtime dependencies (#1046) test: validate MI300 runtime selection and placement (#1045) fix: support ROCm RDNA APU kernels safely (#1044) fix: ROCm GPU enumeration (#1039) Document public packaging installation channels Fix Windows autoupdate import (#1030) Update llama.cpp upstream pin
Summary
gfx942KFD evidence selects a compatible ROCm native runtime instead of the CPU fallbackRoot cause
The issue logs show every model buffer allocated as
CPU_Mapped, while the MI300X (1002:74b5) remained idle. Runtime artifact selection occurred before authoritative HIP enumeration. Without early ROCm architecture evidence, release builds could select the CPU native runtime, after which no placement decision could use the GPU. #1039 discoversgfx_target_versionfrom KFD topology first (90402→gfx942) so the ROCm runtime is loaded. Once that capability is present, the existing resource planner already weights placement by available accelerator memory.This PR is intentionally stacked on #1039 and adds the MI300-specific end-to-end decision coverage requested by #653.
Validation
cargo test -p mesh-llm-hardware-profile --libcargo test -p mesh-llm-host-runtime runtime::split_planning::tests --libcargo check -p mesh-llm-hardware-profile -p mesh-llm-host-runtime -p mesh-llmcargo clippy -p mesh-llm-hardware-profile -p mesh-llm-host-runtime -p mesh-llm --all-targets -- -D warningsjust test-allDepends on #1039. Validates the MI300 path reported in #653.
Summary by CodeRabbit