[dynamo, 3.14] Ensure typing.Union is correctly traced in Dynamo.

[guilhermeleobas]

Stack from ghstack (oldest at bottom):

• -> [dynamo, 3.14] Ensure typing.Union is correctly traced in Dynamo. #169084

Fixes test_vector_norm_decom_unbacked_checks_cpu from test/test_linalg.py on Python 3.14

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @kadeng @chauhang @amjames @Lucaskabela @jataylo

[pytorch-bot]

🔗 Helpful Links

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

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

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

❗ 2 Active SEVs

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

• Dr CI is temporarily not working due to API fairewall
• Pytorch CI is partially paused for the time being (updated 11/27)

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

[guilhermeleobas]

@pytorchbot merge

[guilhermeleobas]

@pytorchbot merge

[guilhermeleobas]

@pytorchbot rebase

[pytorchmergebot]

Merge failed

Reason: This PR needs a release notes: label
If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

Details for Dev Infra team

Raised by workflow job

[guilhermeleobas]

@pytorchbot merge

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[pytorchmergebot]

Tried to rebase and push PR #169084, but it was already up to date. Try rebasing against main by issuing:
@pytorchbot rebase -b main

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

[cyyever]

@pytorchbot rebase -b main

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

[pytorchmergebot]

Successfully rebased gh/guilhermeleobas/262/orig onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/169084)

[pytorchmergebot]

Merge failed

Reason: New commits were pushed while merging. Please rerun the merge command.

Details for Dev Infra team

Raised by workflow job

[cyyever]

@pytorchbot rebase -b main

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

[pytorchmergebot]

Successfully rebased gh/guilhermeleobas/262/orig onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/169084)

[cyyever]

@pytorchmergebot merge -f "Pending ROCm"

[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