KEMBAR78
[PyTorch] Add the lazy init call for p2p access function (#1991) by banitag1 · Pull Request #108589 · pytorch/pytorch · GitHub
Skip to content

[PyTorch] Add the lazy init call for p2p access function (#1991) #108589

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

[PyTorch] Add the lazy init call for p2p access function (#1991) #108589

wants to merge 1 commit into from

Conversation

@banitag1
Copy link
Contributor

@banitag1 banitag1 commented Sep 5, 2023

Summary: Pull Request resolved: pytorch/FBGEMM#1991

Test Plan: sandcastle

Reviewed By: zdevito

Differential Revision: D48939723

@zdevito @facebook-github-bot
[PyTorch] Add the lazy init call for p2p access function (pytorch#1991)
4865c30 
Summary: Pull Request resolved: pytorch/FBGEMM#1991

Test Plan: sandcastle

Reviewed By: zdevito

Differential Revision: D48939723
@pytorch-bot
Copy link

pytorch-bot bot commented Sep 5, 2023 •
edited
Loading

🔗 Helpful Links

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

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

❗ 1 Merge Blocking SEVs

There is 1 active merge blocking SEVs. Please view them below:

If you must merge, use @pytorchbot merge -f.

✅ No Failures

As of commit 4865c30 with merge base fac7a1f (image):
💚 Looks good so far! There are no failures yet. 💚

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

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D48939723

@github-actions
Copy link
Contributor

github-actions bot commented Sep 5, 2023

This PR needs a release notes: label

If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@facebook-github-bot
Copy link
Contributor

@pytorchbot merge

(Initiating merge automatically since Phabricator Diff has merged)

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Sep 6, 2023
@pytorchmergebot
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@zdevito zdevito zdevito approved these changes

Assignees

No one assigned

Labels

ciflow/trunk Trigger trunk jobs on your pull request fb-exported Merged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@banitag1 @facebook-github-bot @pytorchmergebot @zdevito