Do not treat all dense tensors as isTensorSubclassLike

[ezyang]

Stack from ghstack (oldest at bottom):

• -> Do not treat all dense tensors as isTensorSubclassLike #79098

Fixes #79079

Signed-off-by: Edward Z. Yang ezyang@fb.com

[facebook-github-bot]

🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/79098
• 📄  Preview Python docs built from this PR
• 📄  Preview C++ docs built from this PR
• ❓Need help or want to give feedback on the CI? Visit our office hours
• ↩️  [fb-only] Re-run with SSH instructions

❌ 1 New Failures

As of commit 9177aa5 (more details on the Dr. CI page):

Expand to see more

---

• 1/1 failures introduced in this PR

---

🕵️ 1 new failure recognized by patterns

The following CI failures do not appear to be due to upstream breakages

pull / linux-xenial-cuda11.3-py3.7-gcc7 / test (default, 3, 4, linux.4xlarge.nvidia.gpu) (1/1)

Step: "Test" (full log | diagnosis details | 🔁 rerun)

2022-06-09T04:09:36.3937771Z RuntimeError: test_modules failed!

2022-06-09T04:09:35.6760846Z 
2022-06-09T04:09:35.6761054Z FAILED (errors=3, skipped=565, expected failures=12, unexpected successes=3)
2022-06-09T04:09:35.6761302Z 
2022-06-09T04:09:35.6761433Z Generating XML reports...
2022-06-09T04:09:35.7829260Z Generated XML report: test-reports/python-unittest/test_modules/TEST-TestModuleCUDA-20220609040857.xml
2022-06-09T04:09:36.3931469Z Traceback (most recent call last):
2022-06-09T04:09:36.3931883Z   File "test/run_test.py", line 1077, in <module>
2022-06-09T04:09:36.3934405Z     main()
2022-06-09T04:09:36.3934686Z   File "test/run_test.py", line 1055, in main
2022-06-09T04:09:36.3937353Z     raise RuntimeError(err_message)
2022-06-09T04:09:36.3937771Z RuntimeError: test_modules failed!
2022-06-09T04:09:36.9387408Z + cleanup
2022-06-09T04:09:36.9387705Z + retcode=1
2022-06-09T04:09:36.9387972Z + set +x
2022-06-09T04:09:36.9439392Z ##[error]Process completed with exit code 1.
2022-06-09T04:09:36.9489498Z ##[group]Run pytorch/pytorch/.github/actions/get-workflow-job-id@master
2022-06-09T04:09:36.9489893Z with:
2022-06-09T04:09:36.9490477Z   github-token: ***
2022-06-09T04:09:36.9490708Z env:
2022-06-09T04:09:36.9490932Z   IN_CI: 1
2022-06-09T04:09:36.9491164Z   IS_GHA: 1

---

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.

[albanD]

SGTM

[ezyang]

@pytorchbot merge

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here

[pytorchmergebot]

Merge failed due to Command git -C /home/runner/actions-runner/_work/pytorch/pytorch cherry-pick -x fb53d3da43f64f2be0c632679655149fd64e9061 returned non-zero exit code 1

Auto-merging test/test_profiler.py
CONFLICT (content): Merge conflict in test/test_profiler.py
error: could not apply fb53d3da43... Do not treat all dense tensors as isTensorSubclassLike
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

Raised by https://github.com/pytorch/pytorch/actions/runs/2465208500

[ezyang]

@pytorchbot merge -g

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here

[github-actions]

Hey @ezyang.
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.