Store type(module) in the module stack

[SherlockNoMad]

Stack from ghstack (oldest at bottom):

• -> Store type(module) in the module stack #87149

• As requested by quantization team, it prefer storing type(module) in the module stack.
• Consequently, as module stack gets verbose, we skip printing module stack in the gm.print_readable()

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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

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

❗ 3 Active SEVs

There are 3 currently active SEVs. If your PR is affected, please view them below:

• Actions might queue/get cancelled/not get scheduled
• Conda ChecksumMismatchError error blocking CI jobs
• Run Simulator Tests fails with Segmentation Fault #87207

❌ 7 Failures

As of commit 8ba8a4b:

The following jobs have failed:

• android-emulator-build-test / build-and-test
• ios-12-5-1-x86-64 / build
• macos-12-py3-arm64 / test (default, 1, 2, macos-m1-12)
• macos-12-py3-arm64 / test (default, 2, 2, macos-m1-12)
• macos-12-py3-arm64 / test (functorch, 1, 1, macos-m1-12)
• macos-12-py3-x86-64 / build
• macos-12-py3-x86-64-lite-interpreter / build

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

[jerryzh168]

thanks!

[SherlockNoMad]

@pytorchbot merge -f "flaky macOS CI"

[pytorchmergebot]

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

[github-actions]

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