-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Use the same checks in all grid_sampler functions
#74635
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
Fixes #73187. [ghstack-poisoned]
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit 408b8cd (more details on the Dr. CI page):
🕵️ 3 new failures recognized by patternsThe following CI failures do not appear to be due to upstream breakages
|
|
(putting @albanD in reviewers for visibility, feel free to re-assign) |
|
basically, the idea here is this: move the checks from the top-level |
|
the changes to error messages in old files are due to me moving/splitting the checks for 4d/5d cases |
albanD
left a comment
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.
Thanks for the cleanup. it looks quite good. High level questions:
- Are the CI failures relevant?
- It would be much simpler if the utils functions were only in the header (no cpp) file. That would remove the need to update the build systemsss. Do you think that would be a better way to go here to make this change simpler?
|
@albanD i'll look at the ci failures tomorrow probably, but to answer your second question: i think the current way is actually the easiest. i also felt uncomfortable about adding new files, but i think you just have to do it for the following reasons:
you need to avoid exposing
i'd need to include the header before the assert (or it won't compile), and it would be undermining the work done by peter in the pr i linked above (#66979). so i simply don't see any other way to do it. i did try the header-only thing as well, i even have a wip branch with that work already. i just need to double check that it actually works and i should be able to share it. but given the things i mentioned above, should i? cc @peterbell10 |
Fixes #73187. [ghstack-poisoned]
|
pushed a small update to fix the linter issue and rocm builds. not sure if it fixes everything because i can only do cuda builds locally atm. let's see what ci thinks |
Fixes #73187. [ghstack-poisoned]
|
pushed an update implementing the header-only approach -- no build system changes, let's see what ci thinks |
|
i wonder if i should write more test cases such that i trigger every TORCH_CHECK. but it might be tricky, not sure it's worth it. thoughts? |
peterbell10
left a comment
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.
TensorBase related stuff looks good to me. Didn't check the grid_sampler changes too closely but the tests are broken at the moment.
albanD
left a comment
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.
Looks good!
Thanks for taking the time to update the code to work well with TensorMeta!
|
The newly added test is failing in CI though |
|
i'll take a look at the failures. will follow up later |
Fixes #73187. [ghstack-poisoned]
|
couldn't make sense of the ci errors, so rebased and pushed. let's wait for ci again and see if this changes anything |
|
will fix this rocm failure once the ci is done: |
Fixes #73187. [ghstack-poisoned]
|
pushed a fix for the rocm failure |
|
does ci need to be updated? https://github.com/pytorch/pytorch/runs/5761511611 |
|
The hud: https://hud.pytorch.org/ is a good place to check CI status. There is currently a SEV there meaning that something is broken on their end yes. |
|
@albanD has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
|
upd: nevermind, replied with the wrong stack in mind. but that test is still pretty important tho |
|
i've just triggered a re-run because it looks like this is fixed on hud(?). not sure if i need to rebase again tho |
|
The new CI run looks good. So I'm going to try to land as-is. Will let you know if this needs a rebase. |
|
Hey @nkaretnikov. |
|
The cuda test failures were actually real and this broke master: https://github.com/pytorch/pytorch/runs/5789789694?check_suite_focus=true. Reverting. |
|
This pull request has been reverted by 0ce02ea. To re-land this change, please open another pull request, assignthe same reviewers, fix the CI failures that caused the revert and make sure that the failing CI runs on the PR by applying the proper ciflow label (e.g., ciflow/trunk). |
|
This pull request has been reverted by 0ce02ea. To re-land this change, please open another pull request, assignthe same reviewers, fix the CI failures that caused the revert and make sure that the failing CI runs on the PR by applying the proper ciflow label (e.g., ciflow/trunk). |
Stack from ghstack:
grid_samplerfunctions #74635Fixes #73187.
Differential Revision: D35284563