Skip to content

Improve error msg on _lazy_init() error #134159

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

Improve error msg on _lazy_init() error #134159

wants to merge 1 commit into from

Conversation

nautsimon
Copy link
Member

Reviewed By: hanzlfs

Differential Revision: D61627609

@nautsimon @facebook-github-bot
Improve error msg on _lazy_init() error
023ffef 
Reviewed By: hanzlfs

Differential Revision: D61627609
@pytorch-bot
Copy link

pytorch-bot bot commented Aug 21, 2024 •
edited
Loading

🔗 Helpful Links

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

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

✅ You can merge normally! (1 Unrelated Failure)

As of commit 023ffef with merge base 0870398 (image):

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

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: D61627609

@nautsimon nautsimon requested a review from hanzlfs August 21, 2024 22:11
@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Aug 21, 2024
@nautsimon
Copy link
Member Author

Failing CI is failing on master, will merge

@nautsimon nautsimon added the better-engineering Relatively self-contained tasks for better engineering contributors label Aug 22, 2024
@nautsimon
Copy link
Member Author

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 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.

Details for Dev Infra team Raised by workflow job

@nautsimon nautsimon added the topic: not user facing topic category label Aug 22, 2024
@nautsimon
Copy link
Member Author

@pytorchbot merge

@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

pytorchmergebot pushed a commit to mayank31398/pytorch that referenced this pull request Aug 23, 2024
@nautsimon @pytorchmergebot
Improve error msg on _lazy_init() error (pytorch#134159)
fdb3e62 
Reviewed By: hanzlfs

Differential Revision: D61627609

Pull Request resolved: pytorch#134159
Approved by: https://github.com/hanzlfs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@hanzlfs hanzlfs hanzlfs approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

better-engineering Relatively self-contained tasks for better engineering contributors ciflow/trunk Trigger trunk jobs on your pull request fb-exported Merged topic: not user facing topic category

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@nautsimon @facebook-github-bot @pytorchmergebot @hanzlfs