Skip to content

fix(ci): set TMS_CUDA_MAJOR via uv extra-build-variables - #3905

Merged
kajalj22 merged 1 commit into
mainfrom
kajalj/tms-cuda-major-extra-build-var
Aug 29, 2026
Merged

fix(ci): set TMS_CUDA_MAJOR via uv extra-build-variables#3905
kajalj22 merged 1 commit into
mainfrom
kajalj/tms-cuda-major-extra-build-var

Conversation

@kajalj22

Copy link
Copy Markdown
Contributor

Summary

  • torch-memory-saver's build backend needs TMS_CUDA_MAJOR when uv builds it during uv lock. Declare it once via [tool.uv.extra-build-variables] in pyproject.toml so every caller of uv lock/uv sync (GitHub Actions, nemo-ci, local dev) picks it up automatically — no per-CI-system shell/sed logic needed.
  • Reverts the GitHub Actions-only workaround from fix(ci): set CUDA major for torch-memory-saver lock generation #3862 (sed-derive + export before uv lock), which this supersedes.

Test plan

  • uv lock succeeds and lockfile includes torch-memory-saver without manually exporting TMS_CUDA_MAJOR
  • CI "Generate lockfile" step passes

torch-memory-saver's build backend needs TMS_CUDA_MAJOR when uv invokes
its build backend during lockfile generation. Declare it once via uv's
extra-build-variables so uv lock/sync pick it up automatically in every
CI system, instead of deriving it via shell/sed in each caller (#3862,
whose GitHub Actions workaround is reverted here as no longer needed).

Signed-off-by: Kajal Jain <kajalj@nvidia.com>
@kajalj22
kajalj22 requested review from a team as code owners August 29, 2026 02:09
@copy-pr-bot

copy-pr-bot Bot commented Aug 29, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@github-actions github-actions Bot added the CI Relating to CI label Aug 29, 2026

@terrykong terrykong left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does the env need to be re locked?

@kajalj22

Copy link
Copy Markdown
Contributor Author

/ok to test e1d9abc

@terrykong terrykong left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved. i locked locally and i guess the env doesn't need to be re-locked. looks like env vars don't get saved in lock so technically aren't part of what it determines as equivalency

@kajalj22

Copy link
Copy Markdown
Contributor Author

does the env need to be re locked?

UV.lock is valid - checked

@kajalj22
kajalj22 enabled auto-merge (squash) August 29, 2026 02:27
@kajalj22
kajalj22 disabled auto-merge August 29, 2026 02:27
@kajalj22
kajalj22 merged commit 545ba70 into main Aug 29, 2026
46 of 47 checks passed
@kajalj22
kajalj22 deleted the kajalj/tms-cuda-major-extra-build-var branch August 29, 2026 02:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Relating to CI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants