build: AUT-1615 add torch-memory-saver dev dependency - #6701
Conversation
Signed-off-by: svcnemo-autobot <svcnemo-autobot@nvidia.com>
|
This PR has been automatically converted to draft because all PRs must start as drafts. When you are ready for review, click Ready for Review to begin the review process. This will:
See the contribution guide for more details. |
Signed-off-by: svcnemo-autobot <svcnemo-autobot@nvidia.com>
|
/ok to test 705c2e0 |
Signed-off-by: svcnemo-autobot <svcnemo-autobot@nvidia.com>
Signed-off-by: svcnemo-autobot <svcnemo-autobot@nvidia.com>
Signed-off-by: svcnemo-autobot <svcnemo-autobot@nvidia.com>
|
/ok to test 511b0ef |
Signed-off-by: svcnemo-autobot <svcnemo-autobot@nvidia.com>
Head branch was pushed to by a user without write access
|
/ok to test a848e09 |
|
@svcnemo-autobot fetch and merge upstream/main |
|
💬 I’m fetching and merging the current upstream |
|
/ok to test b800152 |
|
🔄 Merge queue validation started! You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/32460128637 |
|
🔄 Merge queue validation started! You can track the progress here: https://github.com/NVIDIA/Megatron-LM/actions/runs/32466798875 |
Signed-off-by: svcnemo-autobot <svcnemo-autobot@nvidia.com> Signed-off-by: Kezhi Kong <kezhik@kezhik-mlt.client.nvidia.com>
Bumps the Megatron-Bridge submodule (nesting Megatron-LM at 7c9c3a027, which pins emerging-optimizers@v0.3.0) and RL's own constraint-dependencies pin to match, per <NVIDIA/Megatron-LM#6701>. The automated mbridge-bump pipeline (nemo-ci) could not do this on its own: it bumps only the submodule, not RL's root pin, so uv lock failed with a conflicting-URL error until both moved together in one commit. Signed-off-by: Kajal Jain <kajalj@nvidia.com>
Bumps the Megatron-Bridge submodule (nesting Megatron-LM at 7c9c3a027, which pins emerging-optimizers@v0.3.0) and RL's own constraint-dependencies pin to match, per <NVIDIA/Megatron-LM#6701>. The automated mbridge-bump pipeline (nemo-ci) could not do this on its own: it bumps only the submodule, not RL's root pin, so uv lock failed with a conflicting-URL error until both moved together in one commit. Signed-off-by: Kajal Jain <kajalj@nvidia.com>
Bumps the Megatron-Bridge submodule (nesting Megatron-LM at 7c9c3a027, which pins emerging-optimizers@v0.3.0) and RL's own constraint-dependencies pin to match, per <NVIDIA/Megatron-LM#6701>. The automated mbridge-bump pipeline (nemo-ci) could not do this on its own: it bumps only the submodule, not RL's root pin, so uv lock failed with a conflicting-URL error until both moved together in one commit. Signed-off-by: Kajal Jain <kajalj@nvidia.com>
Bumps the Megatron-Bridge submodule (nesting Megatron-LM at 7c9c3a027, which pins emerging-optimizers@v0.3.0) and RL's own constraint-dependencies pin to match, per <NVIDIA/Megatron-LM#6701>. The automated mbridge-bump pipeline (nemo-ci) could not do this on its own: it bumps only the submodule, not RL's root pin, so uv lock failed with a conflicting-URL error until both moved together in one commit. Signed-off-by: Kajal Jain <kajalj@nvidia.com>
Signed-off-by: svcnemo-autobot <svcnemo-autobot@nvidia.com>
Background
Megatron-LM uses
torch_memory_saverfor inference and RL memory offloading, but it is absent from the development environment.What changed
torch-memory-saverto thedevextra.9bc9a442e6d108c7b7903def199896a005143aaf(tagv0.0.10b1).uv.lockwith that exact revision.TMS_CUDA_MAJORfrom the active CUDA toolkit.Details
flowchart LR A[GitHub commit] --> B[dev dependency] C[active CUDA toolkit] --> D[source build] B --> DTested
uv lock --checkbash -n docker/common/install.shgit diff --check