[PT2][Inductor]Add unbind node normalization

[mengluy0125]

Summary: Normalize unbind nodes for the followup split_cat pattern detection and node removals

Test Plan:

buck2 test //caffe2/test/inductor:split_cat_fx_passes

Buck UI: https://www.internalfb.com/buck2/f42297c2-2595-40a2-b270-5cec026f2fe4
Test UI: https://www.internalfb.com/intern/testinfra/testrun/17451448578242323
Network: Up: 132KiB Down: 88KiB (reSessionID-fc725143-317a-42a9-bc7e-0bbab6ef9e5c)
Jobs completed: 27. Time elapsed: 3:09.2s.
Cache hits: 0%. Commands: 1 (cached: 0, remote: 0, local: 1)
Tests finished: Pass 11. Fail 0. Fatal 0. Skip 0. Build failure 0

buck2 test mode/opt mode/inplace caffe2/test/inductor/fb:test_split_cat_fx_passes_aten_fb

Differential Revision: D53964593

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler @amjames

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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 the bot commands wiki or our office hours

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

✅ You can merge normally! (5 Unrelated Failures)

As of commit 36a3a45 with merge base 8fa6340 ():

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• trunk / linux-focal-cuda12.1-py3.10-gcc9 / test (nogpu_AVX512, 1, 1, linux.2xlarge) (gh)
  dynamo/test_trace_rules.py::TraceRuleTests::test_torch_name_rule_map_updated
• trunk / linux-focal-cuda12.1-py3.10-gcc9 / test (nogpu_NO_AVX2, 1, 1, linux.2xlarge) (gh)
  dynamo/test_trace_rules.py::TraceRuleTests::test_torch_name_rule_map_updated
• trunk / macos-12-py3-arm64 / test (default, 1, 3, macos-m1-12) (gh)
  dynamo/test_trace_rules.py::TraceRuleTests::test_torch_name_rule_map_updated

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• trunk / win-vs2019-cpu-py3 / test (default, 1, 3, windows.4xlarge.nonephemeral) (gh)
  test_torch.py::TestTorchDeviceTypeCPU::test_grad_scaling_autocast_foreach_cpu
• trunk / win-vs2019-cpu-py3 / test (default, 2, 3, windows.4xlarge.nonephemeral) (gh)
  test_optim.py::TestSWAUtils::test_averaged_model_all_devices_ema_True

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

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D53964593

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D53964593

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D53964593

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D53964593

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D53964593

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D53964593

[facebook-github-bot]

@pytorchbot merge -f 'Landed internally'

(Initiating merge automatically since Phabricator Diff has merged, using force because this PR might not pass merge_rules.json but landed internally)

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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