Skip to content

Add additional CUDA error handling macros #74865

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
r-barnes wants to merge 1 commit into from
Closed

Add additional CUDA error handling macros #74865

r-barnes wants to merge 1 commit into from

Conversation

@r-barnes
Copy link
Contributor

@r-barnes r-barnes commented Mar 28, 2022

Test Plan: Sandcastle

Differential Revision: D35194530

@r-barnes @facebook-github-bot
Add additional CUDA error handling macros
62526a0 
Test Plan: Sandcastle

Differential Revision: D35194530

fbshipit-source-id: 883e85dc5db08a150cf6270ca45c9164032386b5
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Mar 28, 2022 •
edited
Loading

🔗 Helpful links

💊 CI failures summary and remediations

As of commit 62526a0 (more details on the Dr. CI page):

💚 💚 Looks good so far! There are no failures yet. 💚 💚

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Mar 28, 2022

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

facebook-github-bot pushed a commit that referenced this pull request Mar 29, 2022
@r-barnes @facebook-github-bot
Add additional CUDA error handling macros (#74865)
919ddf6 
Summary:
Introduces additional ways of handling CUDA errors that allow automated linters to detect if errors are being handled.

Pull Request resolved: #74865

Test Plan: Sandcastle

Reviewed By: ngimel

Differential Revision: D35194530

fbshipit-source-id: f4fe61594edbfd81e97a4b605935961b893df167
@github-actions
Copy link
Contributor

github-actions bot commented Mar 29, 2022

Hey @r-barnes.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

@WBobby WBobby mentioned this pull request Aug 17, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

cla signed fb-exported

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@r-barnes @facebook-github-bot