🔗 Helpful Links

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

• 📄 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 our office hours

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

✅ No Failures

As of commit 2b33223:
💚 Looks good so far! There are no failures yet. 💚

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

This will need to be cherry-picked into core release, right?

This will need to be cherry-picked into core release, right?

I don't think so as this is just a follow-up PR for #87017. And, as #87017 is not going to be cherrypicked, this should not.

And, the CI is broken for nightly release. Our RC release is fine.

@pytorchbot merge -g

Merge started

Your change will be merged once all checks on your PR pass since you used the green (-g) flag (ETA: 0-4 Hours).

Learn more about merging in the wiki.

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

Merge failed

Reason: The following mandatory check(s) failed (Rule superuser):

• pull

Dig deeper by viewing the failures on hud

@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: The following mandatory check(s) failed (Rule superuser):

• pull

Dig deeper by viewing the failures on hud

@pytorchbot rebase

@pytorchbot successfully started a rebase job. Check the current status here

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

@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