New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BE] Use nested namespaces in sparse #97581
Conversation
copilot:summary
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/97581
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 FailuresAs of commit 63394b7: NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@pytorchbot merge |
Merge startedYour 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 failedReason: 1 jobs have failed, first few of them are: trunk / linux-bionic-cuda11.8-py3.10-gcc7 / test (default, 3, 5, linux.4xlarge.nvidia.gpu) Details for Dev Infra teamRaised by workflow job |
@pytorchbot merge -f "TestTorch::test_typed_storage_deprecation_warning is due to trunk regressions, perhaps fixed by #97628 " |
Merge startedYour 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 |
🤖 Generated by Copilot at 59a5205
This pull request refactors the namespace declarations in several files under
aten/src/ATen/native/sparse
to use a more concise and consistent syntax. This improves the readability and reusability of the sparse tensor operations code.Also, do not rely on deprecated
TensorBase::data
and instead useTensorBase::data_ptr