-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[memory snapshot] add 'address' key to block #107171
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
Conversation
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/107171
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit d4d73e6 with merge base 2e73c86 ( 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 |
The merge job was canceled. If you believe this is a mistake,then you can re trigger it through pytorch-bot. |
[ghstack-poisoned]
This change is to match the behavior of _record_memory_history which was recently changed to enable history recording on all devices rather than the current one. It prevents confusing situations where the observer was registered before the device was set for the training run. It also ensures the allocators have been initialized in the python binding just in case this is the first call to the CUDA API. Fixes #107330 Pull Request resolved: #107399 Approved by: https://github.com/eellison ghstack dependencies: #107171
Pull Request resolved: #107660 Approved by: https://github.com/albanD ghstack dependencies: #107171, #107399
Stack from ghstack (oldest at bottom):