Skip to content
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

Avoid calling allclose in the backward if there are tensor subclasses #91444

Closed
wants to merge 2 commits into from

Conversation

lezcano
Copy link
Collaborator

@lezcano lezcano commented Dec 28, 2022

Stack from ghstack (oldest at bottom):

allclose it's data-dependent (returns a bool) so it does not play well
with functorch. We are skipping that check in the context of subclasses
to avoid hard errors.

Partially fixes #90499

cc @zou3519 @Chillee @samdow @soumith

`allclose` it's data-dependent (returns a bool) so it does not play well
with functorch. We are skipping that check in the context of subclasses
to avoid hard errors.

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Dec 28, 2022

🔗 Helpful Links

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

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

❌ 1 Failures

As of commit cbb629d:

NEW FAILURES - The following jobs have failed:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

lezcano added a commit that referenced this pull request Dec 28, 2022
`allclose` it's data-dependent (returns a bool) so it does not play well
with functorch. We are skipping that check in the context of subclasses
to avoid hard errors.

ghstack-source-id: 43e9d6e23047be7c6fed4198ea32408531dc7688
Pull Request resolved: #91444
@lezcano lezcano added module: functorch Pertaining to torch.func or pytorch/functorch release notes: functorch release notes category; Pertaining to torch.func or pytorch/functorch labels Dec 28, 2022
… subclasses"


`allclose` it's data-dependent (returns a bool) so it does not play well
with functorch. We are skipping that check in the context of subclasses
to avoid hard errors.

Partially fixes #90499

cc zou3519 Chillee samdow soumith

[ghstack-poisoned]
lezcano added a commit that referenced this pull request Dec 28, 2022
`allclose` it's data-dependent (returns a bool) so it does not play well
with functorch. We are skipping that check in the context of subclasses
to avoid hard errors.

ghstack-source-id: cc6278acefadb56f61e946f3764f4675274cbd9b
Pull Request resolved: #91444
Copy link
Collaborator

@albanD albanD left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure

@lezcano
Copy link
Collaborator Author

lezcano commented Dec 28, 2022

@pytorchbot merge -f "unrelated error"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

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

@facebook-github-bot facebook-github-bot deleted the gh/Lezcano/168/head branch June 8, 2023 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Merged module: functorch Pertaining to torch.func or pytorch/functorch open source release notes: functorch release notes category; Pertaining to torch.func or pytorch/functorch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants