Skip to content

cp: Merge main to super-v3.5-posttraining - 2026-08-05 - #3482

Merged
yfw merged 22 commits into
super-v3.5-posttrainingfrom
yifu/super-merge-main-20260803
Aug 5, 2026
Merged

cp: Merge main to super-v3.5-posttraining - 2026-08-05#3482
yfw merged 22 commits into
super-v3.5-posttrainingfrom
yifu/super-merge-main-20260803

feat: nccl v2.30.7 bump (#3453)

8677447
Select commit
Loading
Failed to load commit list.
DCO / DCO required action Aug 5, 2026 in 0s

DCO

There are 7 commits incorrectly signed off. This means that the author(s) of these commits failed to include a Signed-off-by line in their commit message.

To avoid having PRs blocked in the future, always include Signed-off-by: Author Name <authoremail@example.com> in every commit message. You can also do this automatically by using the -s flag (i.e., git commit -s).

Here is how to fix the problem so that this code can be merged.


Rebase the branch

If you have a local git environment and meet the criteria below, one option is to rebase the branch and add your Signed-off-by lines in the new commits. Please note that if others have already begun work based upon the commits in this branch, this solution will rewrite history and may cause serious issues for collaborators (described in the git documentation under "The Perils of Rebasing").

You should only do this if:

  • You are the only author of the commits in this branch
  • You are absolutely certain nobody else is doing any work based upon this branch
  • There are no empty commits in the branch (for example, a DCO Remediation Commit which was added using --allow-empty)

To add your Signed-off-by line to every commit in this branch:

  1. Ensure you have a local copy of your branch by checking out the pull request locally via command line.
  2. In your local branch, run: git rebase HEAD~22 --signoff
  3. Force push your changes to overwrite the branch: git push --force-with-lease origin yifu/super-merge-main-20260803

Summary

Commit sha: a1af9ae, Author: Anish Mahishi, Committer: GitHub; Expected "Anish Mahishi 20884035+macandro96@users.noreply.github.com", but got "Anish Mahishi amahishi@nvidia.com".
Commit sha: a704801, Author: aroshanghias-nvd, Committer: GitHub; Can not find "aroshanghias-nvd aroshanghias@nvidia.com", in ["Ali Roshan Ghias aroshanghias@nvidia.com", "Yi-Fu Wu yifu.wu@gmail.com"].
Commit sha: 8fb82ca, Author: Erin, Committer: GitHub; Can not find "Erin 14718778+hchings@users.noreply.github.com", in ["Erin Ho erinh@nvidia.com", "Erin Ho 14718778+hchings@users.noreply.github.com"].
Commit sha: f073000, Author: Erin, Committer: GitHub; Expected "Erin 14718778+hchings@users.noreply.github.com", but got "Erin Ho 14718778+hchings@users.noreply.github.com".
Commit sha: 00c2ba5, Author: kajalj22, Committer: GitHub; Expected "kajalj22 kajalj@nvidia.com", but got "Kajal Jain kajalj@nvidia.com".
Commit sha: 89f4d1f, Author: Rayen, Committer: GitHub; Expected "Rayen ruit@nvidia.com", but got "ruit ruit@nvidia.com".
Commit sha: 414b9bb, Author: wdykas, Committer: GitHub; Expected "wdykas wdykas@nvidia.com", but got "William Dykas 73254672+wdykas@users.noreply.github.com".