Skip to content

fix(mori,docker): unblock MORI smoke on containerized RDMA clusters - #452

Closed
speriaswamy-amd wants to merge 5 commits into
mainfrom
speriaswamy/mori-docker-validation-fixes
Closed

speriaswamy-amd wants to merge 5 commits into
mainfrom
speriaswamy/mori-docker-validation-fixes

Conversation

@speriaswamy-amd

Copy link
Copy Markdown
Contributor

Changes

  • docker_lib.py: add --ulimit memlock=-1 (Docker defaults to 8MB; breaks ibv_reg_mr for RDMA)
  • mori_lib.py: export LD_LIBRARY_PATH from torchlib_dir (CVS-004)
  • mori_lib.py: accept test done! for concurrent_put_thread / concurrent_put_imm_thread smoke checks (these binaries do not print PASSED)

Test plan

  • MORI smoke on Alola/TensorWave (concurrent_put_*, shmem)
  • Verify other Docker-launched RDMA suites still launch with unlimited memlock

Made with Cursor

solaiys and others added 5 commits September 14, 2026 22:27
…onfig

Smoke now passes smoke.steps via maxtext_overrides so polls match the
configured step count instead of maxtext_config.steps.

Add dtype, weight_dtype, and quantization to the DSv4-284B maxtext_config so
training sweeps use BF16 weights and avoid GPU OOM after smoke passes.

Signed-off-by: Saravanan Solaiyappan <saravanan.solaiyappan@amd.com>
Point jaxmaxtext READMEs at jaxmaxtext.rst instead of the removed jax.rst
after the how-to guide was renamed.

Signed-off-by: Saravanan Solaiyappan <saravanan.solaiyappan@amd.com>
* removed the values of few variables that were accidently checked in the code

* Addressed the review comment to fix the value of rdma connectivity mode

---------

Signed-off-by: Urvashi Tiwari <urtiwari.com>
Document AMD Node Check under Burn-in / Diag and mention it with MI4XX health tests on the concepts page.

Co-authored-by: Cursor <cursoragent@cursor.com>
Set memlock ulimit only for MORI container launch (ibv_reg_mr needs it;
Docker default 8MB breaks RDMA registration). Export torchlib_dir via
LD_LIBRARY_PATH in mori env script (CVS-004). Accept concurrent_put_thread/
imm_thread completion marker as smoke pass.
@speriaswamy-amd
speriaswamy-amd force-pushed the speriaswamy/mori-docker-validation-fixes branch from 108a730 to 4c858a1 Compare September 17, 2026 23:43
@speriaswamy-amd

Copy link
Copy Markdown
Contributor Author

Replacing with a branch cut from main (previous head was based on release/cvs-0.2.0 and pulled in unrelated release commits).

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.

4 participants