🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/101457

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure

As of commit 7423980:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@pytorchbot label ciflow/inductor ciflow/periodic

@kwen2501 @awgu This is ready for review. The failing tests don't seem related.

@kwen2501 can we get this approved?

@pytorchbot rebase

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

Successfully rebased update-nccl onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout update-nccl && git pull --rebase)

@pytorchbot merge -f "CI failures are not related"

You are not authorized to force merges to this repository. Please use the regular @pytorchmergebot merge command instead

@pytorchbot merge

This PR updates submodules third_party/nccl/nccl

If those updates are intentional, please add "submodule" keyword to PR title/description.

@pytorchbot merge

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Merge failed

Reason: 2 jobs have failed, first few of them are: periodic / win-vs2019-cuda11.8-py3 / test (default, 2, 4, windows.g5.4xlarge.nvidia.gpu), trunk / libtorch-linux-bionic-cuda11.8-py3.7-gcc7 / build

Please note, that compilation filers while building libtorch are real (by likely fixable by updating this container to use gcc-9 instead of gcc-7)

@syed-ahmed can you please rebase this PR ? I think trunk jobs are using gcc9 now: libtorch-linux-bionic-cuda11.8-py3.7-gcc9, the error you are seing now is probably resolved

@pytorchbot rebase

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

Successfully rebased update-nccl onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout update-nccl && git pull --rebase)

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.