Repository navigation
ExecuTorch 1.6.0 for CPU and GPU exports, held from publishing until both apps ship its runtime - #31
Open
alpharomercoma wants to merge 2 commits into
Open
alpharomercoma wants to merge 2 commits into
alpharomercoma wants to merge 2 commits into
Conversation
…n 1.5.1, and nothing newer than the apps' runtime publishes 1.6.0 needs torch 2.15.0 and Python 3.11 or newer. XNNPACK and Vulkan move to it. QNN stays on 1.5.1 with QAIRT 2.37 (QNN_EXECUTORCH_VERSION), because 1.6.0's wheel compiles with QAIRT 2.51 and both apps ship qnn-runtime 2.39. MediaTek stays on 1.5.1 (MTK_EXECUTORCH_VERSION), because mtk_converter is cp310 only and 1.6.0 has no cp310 wheel. An older program loads on the next runtime, never the reverse, so APP_RUNTIME_VERSION holds publishing until both apps ship the exporter's release: - publish refuses a report built newer than APP_RUNTIME_VERSION - the export workflows stop at their first step when asked to publish such a build (python -m pipeline publish-hold); a build-only run still goes through - the watcher leaves a held backend's models pending and dispatches the later stages config.json gives every variant its own runtime_version, and the folder's value is the newest release in it. verify re-measures when the installed ExecuTorch differs from the one a report was verified with (verified_with), and --force re-measures regardless: before this, a re-run returned the stored verdict for any report already gated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
….0 runtime and fresh 1.6.0 builds against 1.5.1's All 368 published .pte files parse under 1.6.0's schema. All 20 CPU files load and run on it, and 15 of 16 gated ones keep their 1.5.1 verdict (Phi-4-mini improves to 8/8). Qwen2.5-Math-1.5B's published file fails the smoke prompt on 1.6.0 while passing its gate; a 1.6.0 rebuild passes both. Fresh 1.6.0 exports pass their gates with the same GPTQ codes. Linux, GPU, phone and the apps' own runtime builds were not measured here. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
CPU (XNNPACK) and GPU (Vulkan) export with ExecuTorch 1.6.0, torch 2.15.0, torchao 0.18.0 and pytorch-tokenizers 1.6.0.
Qualcomm (QNN) stays on 1.5.1 + QAIRT 2.37 (
QNN_EXECUTORCH_VERSION): 1.6.0's wheel compiles with QAIRT 2.51, and both apps ship qnn-runtime 2.39.MediaTek stays on 1.5.1 (
MTK_EXECUTORCH_VERSION):mtk_converteris cp310 only, and 1.6.0 ships no cp310 wheel.Publishing is held by
APP_RUNTIME_VERSION=1.5.1. An older program loads on the next runtime, but nothing is promised the other way, so no file built with a newer release than the apps run gets published:publishrefuses such a report.python -m pipeline publish-hold). A build-only run still goes through.Merging this as it stands pauses CPU/GPU publishing. Setting
APP_RUNTIME_VERSION=1.6.0lifts the hold once ExecuServe and openweights are live on 1.6.0. Both are in Play review now.config.jsongives each variant its ownruntime_version, and the folder's value is the newest release in it.verifyused to return the stored verdict for any report already gated. It now re-measures when the installed ExecuTorch differs from the one recorded inverified_with, and--forcere-measures regardless.Regression results (finding 48)
.ptefiles parse under 1.6.0's schema.Evidence and scripts:
docs/research/evidence/executorch-1.6.0-regression.md. Reviewed adversarially by Codex over five rounds, and every finding was fixed or documented.Test plan
pytest -q: 422 passed, 1 skipped (Python 3.11, torch 2.15.0, executorch 1.6.0);ruff checkandruff format --checkclean.export-xnnpackrun on this branch (publishing off): run 43719116925, SmolLM2-360M-Instruct at 2k.python -m pipeline publish-holdin arequirements/dev.txt-only Python 3.11 env (whatsetup-lightinstalls): it fails xnnpack and vulkan and passes qnn and mtk. The build-only run skips this step, so it was checked separately.🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is enabled.