braodcast in op_le

[kimishpatel]

Stack from ghstack (oldest at bottom):

• -> braodcast in op_le #11568

Differential Revision: D76456398

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 10 New Failures

As of commit 5ef9025 with merge base 2dda7a2 ():

NEW FAILURES - The following jobs have failed:

• Build Presets / windows (pybind) / build (gh)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 128
• Lint / lintrunner / linux-job (gh)
• pull / test-eval_llama-mmlu-linux / linux-job (gh)
  Process completed with exit code 254.
• pull / test-eval_llama-wikitext-linux / linux-job (gh)
  Process completed with exit code 254.
• pull / test-llama-runner-linux (bf16, custom, linux.2xlarge, executorch-ubuntu-22.04-clang12) / linux-job (gh)
  Process completed with exit code 254.
• pull / test-llama-runner-linux (fp32, xnnpack+custom+quantize_kv, linux.2xlarge, executorch-ubuntu-22.04... / linux-job (gh)
  Process completed with exit code 254.
• pull / test-llama-runner-qnn-linux (fp32, qnn_16a16w, qnn) / linux-job (gh)
  Process completed with exit code 254.
• pull / test-models-linux (ic4, xnnpack-quantization-delegation, linux.4xlarge.memory) / linux-job (gh)
  Process completed with exit code 254.
• pull / test-models-linux (mobilebert, xnnpack-quantization-delegation, linux.2xlarge) / linux-job (gh)
  Process completed with exit code 254.
• pull / test-models-linux (w2l, portable, linux.4xlarge.memory) / linux-job (gh)
  Process completed with exit code 254.

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: D76456398

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

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

[manuelcandales]

I think we need to add a check at the top of this op that the dim orders must be the same, because I don't think any of this support different dim orders. But this was a preexisting issue, so, won't hold you on that.

[manuelcandales]

this is introducing the same bug you are fixing for op_mul in #11590

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.