Expect at least one value in the tensor, to extract scalar from

[lucylq]

Summary:
local scalar dense extracts a scalar from a tensor.

Check that the tensor has at least one value

Differential Revision: D86363818

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 4 New Failures, 3 Unrelated Failures

As of commit f9bc5d0 with merge base d300a81 ():

NEW FAILURES - The following jobs have failed:

• pull / android / run-emulator (gh)
  The process '/usr/bin/sh' failed with exit code 255
• pull / unittest / macos / macos-job (gh)
  backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe
• Test CUDA Builds / check-all-cuda-builds (gh)
  Process completed with exit code 1.
• Test CUDA Builds / test-executorch-cuda-build-12.6 / linux-job (gh)
  RuntimeError: Command docker exec -t 6228e09cf56ab4a1b81fe08d029f4747dff29700fa557033449e3ad96a78a9e9 /exec failed with exit code 1

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

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

• pull / unittest / linux / linux-job (gh) (trunk failure)
  backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe
• pull / unittest-editable / linux / linux-job (gh) (trunk failure)
  backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe
• pull / unittest-editable / macos / macos-job (gh) (trunk failure)

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

[meta-codesync]

@lucylq has exported this pull request. If you are a Meta employee, you can view the originating Diff in D86363818.

[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.

[lucylq]

@pytorchbot cherry-pick --onto release/1.0 -c critical

[pytorchbot]

Cherry picking #15627

The cherry pick PR is at #15783 and it is recommended to link a critical cherry pick PR with an issue. The following tracker issues are updated:

• [v1.0.1] Release Tracker #15534 (comment)

Details for Dev Infra team

Raised by workflow job

[zingo]

@lucylq this seem to have broken the size tests for cortex-m in trunk / test-arm-cortex-m-size-test (zephyr-preset) / linux-job :(

[lucylq]

@lucylq this seem to have broken the size tests for cortex-m in trunk / test-arm-cortex-m-size-test (zephyr-preset) / linux-job :(

thank you - putting up a pr to bump it ..