[ROCm][CI] Stabilize MI355 FusedMoE test group - #53025
Conversation
Signed-off-by: Andreas Karatzas <akaratza@amd.com>
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
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.
|
/ci run |
|
✅ Triggered Buildkite CI #84717 for commit |
Signed-off-by: Andreas Karatzas <akaratza@amd.com>
|
/ci run |
|
✅ Triggered Buildkite CI #84754 for commit |
|
Heads up: when the MI355 FusedMoE Layer group is run in CI, this branch still does not come back clean. Worth another look before merge. |
Signed-off-by: Andreas Karatzas <akaratza@amd.com>
Signed-off-by: Andreas Karatzas <akaratza@amd.com>
|
/ci run |
|
✅ Triggered Buildkite CI #84875 for commit |
|
/amd-ci run |
|
✅ Triggered Buildkite AMD CI #12291 for commit |
|
the remaining flydsl failure is fixed in |
3 participants
This PR addresses the three MI355 FusedMoE failures reported by AMD CI build 12250. The MI355 group was introduced by #41100 and exposed a B200-only DeepEP cleanup that #35077 had broadened to every platform, causing rocSHMEM destroy/reinitialize failures on MI355. The EPLB case separately failed after repeatedly registering NIXL memory while iterating the broad layer matrix. This change restores the CUDA SM100-only DeepEP cleanup and selects Gloo only for gfx950 EPLB in this test, while preserving the layer coverage and dedicated NIXL coverage.
torch_glooonly when this test has EPLB enabled on gfx950; no MI355 layer configurations are skipped, and dedicated EPLB execution tests retain NIXL coverage.