fix invalid call to aoti_torch_tensor_copy_

[trieuat]

Fixes #123039

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

[pytorch-bot]

🔗 Helpful Links

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

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

❌ 8 New Failures, 7 Unrelated Failures

As of commit a57c4ed with merge base fb6f627 ():

NEW FAILURES - The following jobs have failed:

• inductor-periodic / cuda12.1-py3.10-gcc9-sm86-periodic-dynamo-benchmarks / test (aot_eager_torchbench, 1, 2, linux.g5.4xlarge.nvidia.gpu) (gh)
  hf_BigBird
• inductor-periodic / cuda12.1-py3.10-gcc9-sm86-periodic-dynamo-benchmarks / test (dynamic_aot_eager_torchbench, 1, 2, linux.g5.4xlarge.nvidia.gpu) (gh)
  hf_BigBird
• inductor-periodic / cuda12.1-py3.10-gcc9-sm86-periodic-dynamo-benchmarks / test (dynamo_eager_torchbench, 1, 2, linux.g5.4xlarge.nvidia.gpu) (gh)
  hf_BigBird
• pull / linux-focal-py3.11-clang10 / test (dynamo, 3, 3, linux.2xlarge) (gh)
  functorch/test_aotdispatch.py::TestAOTAutograd::test_set__and_data_mutation_good
• pull / linux-focal-py3.12-clang10 / test (dynamo, 1, 3, linux.2xlarge) (gh)
  RuntimeError: test_utils 1/1 failed
• pull / linux-focal-py3.12-clang10 / test (dynamo, 2, 3, linux.2xlarge) (gh)
  RuntimeError: test_torch 1/1 failed
• pull / linux-focal-py3.12-clang10 / test (dynamo, 3, 3, linux.2xlarge) (gh)
  Process completed with exit code 1.
• pull / linux-focal-py3.8-clang10 / test (dynamo, 2, 3, linux.2xlarge) (gh)
  ##[error]The operation was canceled.

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

• inductor / rocm6.0-py3.8-inductor / test (inductor, 1, 1, linux.rocm.gpu.2) (gh) (disabled by #123321 but the issue was closed recently and a rebase is needed to make it pass)
  inductor/test_aot_inductor.py::AOTInductorTestNonABICompatibleCuda::test_buffer_mutation_3_non_abi_compatible_cuda
• pull / linux-focal-cuda12.1-py3.10-gcc9-sm86 / test (default, 1, 5, linux.g5.4xlarge.nvidia.gpu) (gh) (disabled by #121166 but the issue was closed recently and a rebase is needed to make it pass)
  inductor/test_max_autotune.py::TestMaxAutotune::test_max_autotune_remote_caching_dynamic_False
• pull / linux-focal-cuda12.1-py3.10-gcc9-sm86 / test (default, 2, 5, linux.g5.4xlarge.nvidia.gpu) (gh) (disabled by #121194 but the issue was closed recently and a rebase is needed to make it pass)
  inductor/test_max_autotune.py::TestMaxAutotune::test_max_autotune_remote_caching_dynamic_True
• trunk / linux-focal-rocm6.0-py3.8 / test (default, 1, 1, linux.rocm.gpu) (gh) (disabled by #117430 but the issue was closed recently and a rebase is needed to make it pass)
  test_cuda.py::TestCuda::test_lazy_init

UNSTABLE - The following jobs failed but were likely due to flakiness present on trunk and has been marked as unstable:

• inductor / cuda12.1-py3.10-gcc9-sm86 / test (aot_inductor_torchbench, 1, 2, linux.g5.4xlarge.nvidia.gpu) (gh) (#120841)
  hf_BigBird
• inductor / cuda12.1-py3.10-gcc9-sm86 / test (dynamic_inductor_torchbench, 1, 2, linux.g5.4xlarge.nvidia.gpu) (gh) (#120841)
  hf_BigBird
• inductor / cuda12.1-py3.10-gcc9-sm86 / test (inductor_torchbench, 1, 2, linux.g5.4xlarge.nvidia.gpu) (gh) (#120841)
  hf_BigBird

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

[facebook-github-bot]

@trieuat has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[desertfire]

I think just setting self.allow_stack_allocation = False here should work.

[desertfire]

SlimDSNN should not trigger this, so the PR shouldn't affect SlimDSNN's generated code.

[facebook-github-bot]

@trieuat has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@pytorchbot merge

(Initiating merge automatically since Phabricator Diff has merged)

[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

[DanilBaibak]

@pytorchbot merge

[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

[pytorchmergebot]

Merge failed

Reason: 5 mandatory check(s) failed. The first few are:

• pull / linux-focal-py3.12-clang10 / test (dynamo, 1, 3, linux.2xlarge)
• pull / linux-focal-py3.12-clang10 / test (dynamo, 2, 3, linux.2xlarge)
• pull / linux-focal-py3.12-clang10 / test (dynamo, 3, 3, linux.2xlarge)
• pull / linux-focal-py3.8-clang10 / test (dynamo, 2, 3, linux.2xlarge)
• pull / linux-focal-py3.11-clang10 / test (dynamo, 3, 3, linux.2xlarge)

Dig deeper by viewing the failures on hud

Details for Dev Infra team

Raised by workflow job

Failing merge rule: Core Maintainers

[desertfire]

@pytorchbot merge -f "CI failures irrelavent"

[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