[aotd] Config to guess_tangents_stride

[IvanKobzarev]

Stack from ghstack (oldest at bottom):

• -> [aotd] Config to guess_tangents_stride #150035

Differential Revision: D71907684

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

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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! (6 Unrelated Failures)

As of commit 7e6458e with merge base d4da0e9 ():

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

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

• linux-binary-libtorch-release / libtorch-cpu-shared-with-deps-release-build / build (gh) (trunk failure)
  Process completed with exit code 1.
• linux-binary-manywheel / manywheel-py3_9-cuda11_8-build / build (gh) (trunk failure)
  Process completed with exit code 1.
• linux-binary-manywheel / manywheel-py3_9-cuda12_6-build / build (gh) (trunk failure)
  Process completed with exit code 1.
• linux-binary-manywheel / manywheel-py3_9-cuda12_8-build / build (gh) (trunk failure)
  Process completed with exit code 1.
• pull / linux-jammy-py3.9-gcc11 / test (backwards_compat, 1, 1, lf.linux.2xlarge) (gh) (trunk failure)
  test_modules_can_be_imported

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

• pull / cuda12.4-py3.10-gcc9-sm75 / test (pr_time_benchmarks, 1, 1, linux.g4dn.metal.nvidia.gpu) (gh) (#149370)
  REGRESSION: benchmark ('aotdispatcher_training_subclass_cpu', 'compile_time_instruction_count') failed, actual result 9986003060 is 1.59% higher than expected 9830000000 ±+1.50% if this is an expected regression, please update the expected results.

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

[IvanKobzarev]

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

[ilyas409]

LGTM

[IvanKobzarev]

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

[facebook-github-bot]

@pytorchbot merge -i

(Initiating merge automatically since Phabricator Diff has merged, merging with -i because oss signals were bypassed internally)

[pytorch-bot]

This PR needs to be approved by an authorized maintainer before merge.

[IvanKobzarev]

@pytorchbot merge -i

[pytorchmergebot]

Merge started

Your change will be merged while ignoring the following 4 checks: pull / cuda12.4-py3.10-gcc9-sm75 / test (pr_time_benchmarks, 1, 1, linux.g4dn.metal.nvidia.gpu), pull / linux-jammy-py3-clang12-executorch / test (executorch, 1, 1, linux.2xlarge), pull / linux-focal-py3.13-clang10 / test (dynamo_wrapped, 2, 3, linux.2xlarge), pull / linux-focal-py3.9-clang10 / test (dynamo_wrapped, 3, 3, linux.2xlarge)

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: Command git -C /home/runner/work/pytorch/pytorch cherry-pick -x b3cd8f3b752d2355ffb9f973571f8a12c9a98036 returned non-zero exit code 1

Auto-merging test/dynamo/test_backward_higher_order_ops.py
CONFLICT (content): Merge conflict in test/dynamo/test_backward_higher_order_ops.py
Auto-merging test/functorch/test_aotdispatch.py
error: could not apply b3cd8f3b752... [aotd] Config to guess_tangents_stride
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"

Details for Dev Infra team

Raised by workflow job

[IvanKobzarev]

@pytorchbot merge -i

[pytorchmergebot]

Merge started

Your change will be merged while ignoring the following 6 checks: pull / cuda12.4-py3.10-gcc9-sm75 / test (pr_time_benchmarks, 1, 1, linux.g4dn.metal.nvidia.gpu), pull / linux-jammy-py3.9-gcc11 / test (backwards_compat, 1, 1, lf.linux.2xlarge), linux-binary-libtorch-release / libtorch-cpu-shared-with-deps-release-build / build, linux-binary-manywheel / manywheel-py3_9-cuda12_6-build / build, linux-binary-manywheel / manywheel-py3_9-cuda11_8-build / build, linux-binary-manywheel / manywheel-py3_9-cuda12_8-build / build

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