Add Buffer Logs to ExecuTorchRuntime Exception flow (#14557)

[psiddh]

Summary:

These logs provide detailed context when an error occurs in ET runtime flow to Android host apps / processes.

Differential Revision: D83113293

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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, 13 Pending, 1 Unrelated Failure

As of commit 2a15f26 with merge base 9283b4e ():

NEW FAILURES - The following jobs have failed:

• pull / test-qnn-wheel-packages-linux (3.10) / linux-job (gh)
  RuntimeError: Command docker exec -t 6fc9baef8626c5a30738569ebd4cd76fe5ccdf9f5c62e96f92cc1caf5e34d366 /exec failed with exit code 1
• pull / test-qnn-wheel-packages-linux (3.11) / linux-job (gh)
  RuntimeError: Command docker exec -t e9fa36e28f41125d915fe75829ef35dc1d76a2e3b343731cc31f4cbc38954cc7 /exec failed with exit code 1
• pull / test-qnn-wheel-packages-linux (3.12) / linux-job (gh)
  RuntimeError: Command docker exec -t 4679773a7bc94595462995dd21382622000e31229e800ad2cf891bfc742e71a6 /exec failed with exit code 1
• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t f6c6effc339b1ea958966013b679b71c5c6fd1fe8fe86d124e78e3a5b71048ab /exec failed with exit code 1

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

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

• pull / unittest / macos / macos-job (gh) (trunk failure)
  exir/tests/test_quant_fusion_pass.py::TestQuantFusionPass::test_embedding_torchao

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

[facebook-github-bot]

@psiddh has exported this pull request. If you are a Meta employee, you can view the originating diff in D83113293.

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

[facebook-github-bot]

@psiddh has exported this pull request. If you are a Meta employee, you can view the originating diff in D83113293.

[facebook-github-bot]

@psiddh has exported this pull request. If you are a Meta employee, you can view the originating diff in D83113293.

[facebook-github-bot]

@psiddh has exported this pull request. If you are a Meta employee, you can view the originating diff in D83113293.

[psiddh]

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

[pytorchbot]

Cherry picking #14557

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

• [v1.0.0] Release Tracker #14288 (comment)

Details for Dev Infra team

Raised by workflow job