Skip to content

Run the MoE planner memory tests in the Megatron CI lane - #958

Merged
bradhilton merged 1 commit into
mainfrom
dalinar/ci-moe-memory-tests
Sep 25, 2026
Merged

bradhilton merged 1 commit into
mainfrom
dalinar/ci-moe-memory-tests

Conversation

@bradhilton

@bradhilton bradhilton commented Sep 25, 2026 •

Copy link
Copy Markdown
Collaborator

tests/unit/test_trainer_rank_moe_memory.py needs Megatron. It came from #877 and was extended by #954's HybridEP pricing and buffer-growth tests. The module imports art.megatron.lora through pytest.importorskip. CI's root unit-test step has no Megatron, so on main (aab5d5416) 52 of its 57 tests were skipped and 5 ran. The skipped ones include the HybridEP tests.

This moves the module into the "Megatron lightweight tests" step, which runs in megatron_runtime/.venv, and ignores it in the root step. That is the pattern the other trainer-rank memory tests already use. Several of those modules import helpers from this one, so it was already importable in that lane; it just wasn't collected. The tests are CPU-only by design. Locally, with CUDA hidden, all 57 pass.

The edits sit in different hunks from #955's workflow change, with unchanged lines between them. #955 wires in that PR's own new test the same way. A three-way merge of the two branches shows no conflicts.

🤖 Generated with Claude Code

The root unit-test environment lacks Megatron, so importorskip skipped 28
of the module's tests there.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@bradhilton
bradhilton merged commit d734e25 into main Sep 25, 2026
7 checks passed
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.

1 participant