[digantdesai]

Stack from ghstack (oldest at bottom):

• [ET][native] Verify bundled LLM samples through the runner #24175
• [ET][native] Bundle LLM prefill and decode samples from export_hf_llm #24174
• [ET][native] Read bundled samples in C++ #24173
• [ET][native] Make the LLM runner's next-token choice pluggable #24172
• -> [ET][native] Bundle sample method calls in .ptn packages #24171

A .ptn can carry recorded method calls under samples/<method>/<set>/
as index.json plus data.safetensors; program loaders ignore them. A
sample is an ordered list of calls from the initial state with no reset
between, so stateful methods such as LLM prefill then teacher-forced decode
can be checked. Tolerance resolves per call, then sample, then set, and
write_samples warns above 1e-3.

write_samples and read_samples live in
exir/_serialize/_ptn_samples.py. The spec is in backends/native/README.md;
review it first.

Authored with Claude Code.

Differential Revision: D125544384

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 New Failure, 2 Cancelled Jobs, 1 Pending

As of commit a1b2448 with merge base 4db778e ():

NEW FAILURE - The following job has failed:

• pull / test-arm-backend-vkml (test_pytest_ops_vkml) / linux-job (gh)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 56

CANCELLED JOBS - The following jobs were cancelled. Please retry:

• pull / test-arm-backend-vkml (test_runtime_vgf) / linux-job (gh)
  [runner-container-hooks] FATAL: received SIGINT
• Test Vulkan Backend / test-vulkan / test-backend-linux (vulkan, operators) / linux-job (gh)
  curl: (56) OpenSSL SSL_read: error:

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

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