-
Notifications
You must be signed in to change notification settings - Fork 22.9k
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
DNNL: fix F.max_pool2d and F.avg_pool2 issue when stride=None #39221
Conversation
💊 CI failures summary and remediationsAs of commit e7ea14f (more details on the Dr. CI page):
ci.pytorch.org: 1 failedThis comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.Please report bugs/suggestions on the GitHub issue tracker or post in the (internal) Dr. CI Users group. This comment has been revised 1 time. |
Can you also please test that backward works? |
@ngimel , the DNNL backward PRs are not merged now, so only forward path can works. |
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.
@ngimel has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
…h#39221) Summary: For F.max_pool2d and F.avg_pool2d, there has **RuntimeErro**r when stride is **None**, this PR sovle it. Pull Request resolved: pytorch#39221 Differential Revision: D22059565 Pulled By: ngimel fbshipit-source-id: 2080e1e010815aedd904c58552e92be9f7443d38
For F.max_pool2d and F.avg_pool2d, there has RuntimeError when stride is None, this PR sovle it.