🔗 Helpful Links

🧪 See artifacts and rendered test results athud.pytorch.org/pr/154759

• 📄 PreviewPython docs built from this PR
• 📄 PreviewC++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit thebot commands wiki or ouroffice hours

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

✅ You can merge normally! (1 Unrelated Failure)

As of commitb89f50a with merge base9cbbc25 ():

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

Attention! native_functions.yaml was changed

If you are adding a new function or defaulted argument to native_functions.yaml, you cannot use it from pre-existing Python frontend code until our FC window passes (two weeks). Split your PR into two PRs, one which adds the new C++ functionality, and one that makes use of it from Python, and land them two weeks apart. Seehttps://github.com/pytorch/pytorch/wiki/PyTorch's-Python-Frontend-Backward-and-Forward-Compatibility-Policy#forwards-compatibility-fc for more info.

Caused by:

• aten/src/ATen/native/native_functions.yaml

Heads up, if there are any bc problems due to this, I don't think it makes sense to fix, we could just leave things in current state, with no pinning validation on sparse load.

@pytorchbot merge

Merge started

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

Learn more about merging in thewiki.

Questions? Feedback? Please reach out to thePyTorch DevX Team