Add debugability comments to DDPOptimizer

[wconstab]

Stack from ghstack (oldest at bottom):

• -> Add debugability comments to DDPOptimizer #89802

cc @mlazos @soumith @voznesenskym @yanboliang @penguinwu @anijain2305 @EikanWang @jgong5 @Guobing-Chen @chunyuan-w @XiaobingSuper @zhuhaozhe @blzheng @Xia-Weiwen @wenzhe-nrv @jiayisunx @desertfire

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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 Failures

As of commit f552f60:

FLAKY - The following jobs failed but were likely due to flakiness present on master:

• macos-12-py3-arm64 / test (default, 2, 2, macos-m1-12)

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

[wconstab]

@pytorchbot merge

[pytorchmergebot]

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

Advanced Debugging

Check the merge workflow status
here

[pytorchmergebot]

Merge failed

Reason: 1 jobs have failed, first few of them are: trunk / macos-12-py3-arm64 / test (default, 2, 2, macos-m1-12)

Details for Dev Infra team

Raised by workflow job

[wconstab]

@pytorchbot merge -f"flaky"

[pytorch-bot]

You need to provide a reason for using force merge, in the format @pytorchbot merge -f 'Explanation'.
The explanation needs to be clear on why this is needed. Here are some good examples:

• Bypass checks due to unrelated upstream failures from ...
• This is a minor fix to ..., which shouldn't break anything
• This is pre-tested in a previous CI run
• Bypass flaky ... check

[wconstab]

@pytorchbot merge -f "flaky"

[pytorch-bot]

You need to provide a reason for using force merge, in the format @pytorchbot merge -f 'Explanation'.
The explanation needs to be clear on why this is needed. Here are some good examples:

• Bypass checks due to unrelated upstream failures from ...
• This is a minor fix to ..., which shouldn't break anything
• This is pre-tested in a previous CI run
• Bypass flaky ... check

[wconstab]

@pytorchbot merge -f "CI is flaky"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

Learn more about merging in the wiki.

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

Advanced Debugging

Check the merge workflow status
here