[https://nvbugs/6236818][ci] Re-enable Verl post-merge CI stage#15935
Conversation
Signed-off-by: Superjomn <328693+Superjomn@users.noreply.github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis change re-enables a previously disabled Slurm test stage, ChangesJenkins Test Configuration
Estimated code review effort: 1 (Trivial) | ~2 minutes Compact metadataRelated Issues: None provided Poem A rabbit hops through Jenkins' halls, 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/bot run --stage-list "DGX_B200-4_GPUs-Verl-Post-Merge-1" |
|
PR_Github #57587 [ run ] triggered by Bot. Commit: |
|
PR_Github #57587 [ run ] completed with state
|
Signed-off-by: Superjomn <328693+Superjomn@users.noreply.github.com>
|
/bot run |
|
PR_Github #57727 [ run ] triggered by Bot. Commit: |
|
/bot run --stage-list "DGX_B200-4_GPUs-Verl-Post-Merge-1" |
|
PR_Github #57740 [ run ] triggered by Bot. Commit: |
|
PR_Github #57727 [ run ] completed with state |
|
PR_Github #57740 [ run ] completed with state
|
…discovery Use nvidia.nvshmem.__path__ instead of __file__ to resolve the pip-installed NVSHMEM package dir. As a namespace package, __file__ is None and os.path.dirname(None) raised TypeError, crashing the shared Verl setup step. Signed-off-by: Chunwei Yan <yanchunwei@outlook.com>
|
/bot run --extra-stage "DGX_B200-4_GPUs-Verl-Post-Merge-1" |
|
PR_Github #57879 [ run ] triggered by Bot. Commit: |
|
PR_Github #57879 [ run ] completed with state
|
|
/bot run --disable-fail-fast --extra-stage "DGX_B200-4_GPUs-Verl-Post-Merge-1" |
|
PR_Github #57943 [ run ] triggered by Bot. Commit: |
|
PR_Github #57943 [ run ] completed with state
|
…pEP build Drop the explicit nvidia-nvshmem-cu13==3.3.20 install, which shadowed the NVSHMEM version PyTorch was built against and broke torch import during the DeepEP build (libtorch_nvshmem.so: undefined symbol nvshmem_selected_device_transport). Resolve NVSHMEM_DIR to the nvshmem package torch already depends on so DeepEP links against the matching version. Signed-off-by: Chunwei Yan <yanchunwei@outlook.com>
|
/bot run --disable-fail-fast --extra-stage "DGX_B200-4_GPUs-Verl-Post-Merge-1" |
|
PR_Github #58002 [ run ] triggered by Bot. Commit: |
…rl DeepEP build The previous approach resolved NVSHMEM_DIR via `import nvidia.nvshmem`, but that package does not exist in the NGC PyTorch 26.04 base image, so the Verl session-setup fixture aborted and all Verl tests errored at setup. DeepEP's deep_ep_cpp extension hard-links the static device archive (-l:libnvshmem_device.a) and host lib (-l:libnvshmem_host.so); the base image ships neither (only libnvshmem_host.so.3 plus a bitcode device lib). Install the nvidia-nvshmem-cu13 wheel pinned to 3.6.5 -- the exact NVSHMEM version this container's torch was built against -- so libtorch_nvshmem.so's versioned symbols (e.g. nvshmem_selected_device_transport@NVSHMEM) still resolve and `import torch` is not broken by shadowing. Verified locally: import torch succeeds with 3.6.5 on LD_LIBRARY_PATH and DeepEP links sm_100/sm_120/sm_90. Signed-off-by: Superjomn <328693+Superjomn@users.noreply.github.com>
|
/bot run --extra-stage "DGX_B200-4_GPUs-Verl-Post-Merge-1" |
|
PR_Github #58009 [ run ] triggered by Bot. Commit: |
|
PR_Github #58002 [ run ] completed with state |
|
PR_Github #58009 [ run ] completed with state |
…IA#15935) Signed-off-by: Superjomn <328693+Superjomn@users.noreply.github.com> Signed-off-by: Chunwei Yan <yanchunwei@outlook.com>
Summary
Re-enables the
DGX_B200-4_GPUs-Verl-Post-Merge-1post-merge CI stage that was previouslydisabled due to https://nvbugs/6236818. The bug is now resolved.
Change: Remove the three disabling comment lines in
jenkins/L0_Test.groovy(around line 4515)and restore the active
DGX_B200-4_GPUs-Verl-Post-Merge-1stage entry.Validation
test_trtllm_abortremains separately waived under https://nvbugs/6272653 (unrelated issue).CI
The re-enabled stage runs automatically in post-merge CI, or can be triggered manually via:
Summary by CodeRabbit