ci: revert bad uv.lock bump and label future bumps with Run functional tests#4730
Merged
ko3n1g merged 2 commits intoMay 11, 2026
Merged
Conversation
This reverts commit e93755e. Signed-off-by: oliver könig <okoenig@nvidia.com>
uv.lock bumps can shift training numerics, so let CI run the full functional suite (100 steps + golden-value compare) rather than the slim default scope. Signed-off-by: oliver könig <okoenig@nvidia.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Contributor
Author
|
/ok to test 354c78f |
balasaajay
approved these changes
May 11, 2026
svcnvidia-nemo-ci
added a commit
that referenced
this pull request
May 12, 2026
Merges 8 commits from main into dev. Dev already contains yesterday's sync (PR #4716) plus follow-up fixes, so this PR only carries main commits made after that sync. Notable changes: - 434368c build(deps): bump nvidia-modelopt to 0.43 (#4723) - e42e2fa ci: Major refactor of release-workflows (#4602) - 33d47e0 [ci] fix: treat cancelled run-main-script step as failure (#4727) - 5123f6a ci: revert bad uv.lock bump and label future bumps with Run functional tests (#4730) - ad58411 Add Python-side guardrail for DeepEP IB limits (#4719) - e93755e chore(beep boop): Bump (main) (2026-05-11) - a2ec5c1 Revert Add Python-side guardrail for HybridEP IB limit (#4718) - 5e31514 Create a Protocol for the MLP layer of TransformerLayer (#3435) Kept dev's pyproject.toml, uv.lock, docker/Dockerfile.ci.dev, and .github/CODEOWNERS (per nightly-sync skill). Ran black + isort on changed Python files.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Claude summary
What
e93755e13a(chore(beep boop 🤖): Bump (main) (2026-05-11)) — the latest automateduv.lockbump onmain. The bump landed a 785-/+894-line lockfile rewrite that needs to be re-cooked through CI with the functional suite..github/workflows/_update_dependencies.yml: attach theRun functional testslabel to every bump PR opened bypeter-evans/create-pull-request, so the functional suite (100 steps + golden-value compare) runs instead of the slim default.Why
A bare
uv.lockbump only triggersmr-github-slimscope, which can mask numerical regressions in pinned deps. Percicdskill, lockfile bumps warrantRun functional tests.