-
Notifications
You must be signed in to change notification settings - Fork 25.5k
update error message in get_backend() more detail_ #141796
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/141796
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 4bb1b0d with merge base 59f14d1 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
pg_store = _world.pg_map[pg] if pg in _world.pg_map else None | ||
|
||
pg_store = _world.pg_map.get(pg, None) | ||
if pg_store is None: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, how did this not get flagged by mypy I wonder.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Skylion007 thank for your checking. I have resolved it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, okay this just raise the error in not_none before, and now it raises it here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Skylion007 Yes, that's correct. There were developers who were confused due to not knowing the cause, so I made it a bit more detailed.
@Skylion007 The current stage is in a waiting state, so may I kindly ask you to check it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@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 / win-vs2019-cpu-py3 / test (default, 3, 3, lf.windows.4xlarge.nonephemeral) Details for Dev Infra teamRaised by workflow job |
You are not authorized to force merges to this repository. Please use the regular |
@pytorchmergebot 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 / win-vs2019-cpu-py3 / test (default, 3, 3, lf.windows.4xlarge.nonephemeral) Details for Dev Infra teamRaised by workflow job |
@pytorchmergebot 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 / win-vs2019-cpu-py3 / test (default, 3, 3, lf.windows.4xlarge.nonephemeral) Details for Dev Infra teamRaised by workflow job |
@kwen2501 Thank you for checking. Could you please merge this PR? The CI was green in the previous iteration. or, How can I retry it? |
Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as |
@pytorchbot merge -r |
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
Signed-off-by: Um Changyong <e7217@naver.com>
Successfully rebased |
e336db5
to
4bb1b0d
Compare
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: 3 mandatory check(s) failed. The first few are: Dig deeper by viewing the failures on hud |
@kwen2501 |
@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 or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command |
@kwen2501 Currently, even though all tests have been completed, the merge is being blocked. Is this something that needs to be addressed by the contributor or maintainer? 😮😮 I appreciate any advice you can provide. |
@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 |
Fixes #ISSUE_NUMBER
When attempting to reconfigure the environment without properly handling the PyTorch-related settings, you may encounter the following message.
Since this message can cause confusion for multiple developers, the purpose of this PR is to suggest additional details to help clarify the situation.
cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o