UFMT torch.utils._sympy.functions

[ezyang]

Stack from ghstack (oldest at bottom):

• Fix bug for comptime.get_local for cells/closures #126637
• -> UFMT torch.utils._sympy.functions #126553

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

cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10

[pytorch-bot]

🔗 Helpful Links

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

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

❌ 1 New Failure

As of commit 97cc422 with merge base 6bcf156 ():

NEW FAILURE - The following job has failed:

• docker-builds / docker-build (linux.12xlarge, pytorch-linux-focal-rocm-n-py3) (gh)
  Process completed with exit code 1.

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

[ezyang]

@pytorchbot merge -f "straightforward"

[pytorch-bot]

You need to provide a reason for using force merge, in the format @pytorchbot merge -f 'Explanation'.
The explanation needs to be clear on why this is needed. Here are some good examples:

• Bypass checks due to unrelated upstream failures from ...
• This is a minor fix to ..., which shouldn't break anything
• This is pre-tested in a previous CI run
• Bypass flaky ... check

[ezyang]

@pytorchbot merge -f "bypass flaky docker build"

[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