Repository navigation
CI builds Vulkan files from the XNNPACK run's GPTQ codes; the 2026-11-09 RTN-to-GPTQ rollout and the checks that proved it - #29
Merged
Conversation
…s to be shown to carry the codes its report names ptecodes reads every int4 linear out of an ExecuTorch 1.5.1 file in execution order: XNNPACK qbint4 filters through each fully-connected node (delegate calls in program order), Vulkan linear_dq8ca_q4gsw weights, scales and per-group code sums. codesmatch requires a file to carry exactly a solve's codes.pt (codes, scales and order); check classifies a file's codes as rounded or solved against its fp32 source with no codes needed; scan and make_tasks run check over an org; verify_hub ties each published file to its byte check, codes hash, gate reference and gate proxy. Every check of the 2026-11-09 GPTQ rollout ran through these. Standalone for now: not wired into the pipeline or CI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…codes, because a Vulkan workflow of its own could only solve again or round to nearest export-vulkan.yml never passed --codes, so every Vulkan file CI built was rounded to nearest. It is gone. export-xnnpack.yml now publishes each window's gated XNNPACK file, then builds the Vulkan file in a Modal Sandbox of its own from the same codes.pt, with that report as --gate-proxy, and publishes it once its twin is on the Hub. A GPU failure or timeout cannot cost the CPU file, but it fails the job. Only GPTQ 8da4w runs of models Vulkan can take get one (export-matrix --with-vulkan). The watcher has no Vulkan stage: watch.BUILT_WITH marks Vulkan dispatched with the XNNPACK run, records it on entries that predate it, and skips a Vulkan line its host run will never build. Publishing keeps every GPU file beside the gate it cites. An XNNPACK commit withdraws a Vulkan window whose proxy names a twin that commit removes or replaces, judged on the tree the commit produces. A Vulkan publish requires that twin at the head it commits onto, on every retry. GitHub releases follow the Hub. --allow-unpublished-twin is the explicit way past these for a twin deliberately not published (SmolLM2-360M). Four Codex review rounds. Both Modal scripts, extracted verbatim, ran on SmolLM2-135M at 2k with real codes: the twin was gated, the Vulkan file built with a proxy naming it, and both passed publish's checks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ates before 2026-10-31 measured nothing The 2026-11-09 rollout rebuilt the 13 repos with Vulkan folders on EC2: twins gated, every file byte-checked against its codes, and every Hub file tied to that evidence. An independent scan matched all 165 CPU and GPU files in the org to their reports. Decided exceptions: - Qwen3-0.6B's XNNPACK files are fp32 linears and its Vulkan folder is withdrawn. - SmolLM2-360M's Vulkan files are gated through an unpublished twin. Research findings: - 43: Qwen3-0.6B loses its tool decision at int4 whether rounded or solved; fp32 linears keep it. - 44: solving on macOS arm64 turns hidden states into NaN, and the Mac's fp32 gate reference is off as well. - 45: how int4 codes read back out of XNNPACK and Vulkan files, and what separates rounded codes from solved ones. The Vulkan section describes the CI change of the previous commit. 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.
Why:
export-vulkan.ymlnever passed--codes, so every Vulkan file CI built was rounded to nearest. On 2026-11-09 every such file on the Hub was replaced by hand. This PR makes CI build them the same way, so new models stop getting round-to-nearest GPU files.CI: each window's Vulkan file is built in its XNNPACK job
export-xnnpack.ymlpublishes the window's gated XNNPACK file. It then builds the Vulkan file in its own Modal Sandbox from the samecodes.pt, with that report as--gate-proxy, and publishes it once its twin is on the Hub.export-matrix --with-vulkan).export-vulkan.ymlis deleted. A workflow of its own could only solve again, giving the CPU and GPU files different codes, or round to nearest.watch.BUILT_WITHmarks Vulkan dispatched with the XNNPACK run.--allow-unpublished-twinis the explicit way past these for a twin deliberately not published (SmolLM2-360M).Tools and docs
tools/codecheck/: reads a.pte's int4 codes back and proves them againstcodes.ptor the fp32 source, plus the Hub verifier. Standalone, not wired into CI.docs/PLAN.md: what is published now..ptefiles.Verification
ruffandpytest(327) pass.require_publishableandrequire_vouched, and both carry the codes exactly (211/211, in execution order).Not exercised: a live GitHub Actions run on Modal. The first model the watcher dispatches after merge will be one;
export-xnnpack.ymlon a small model withpublish_hf: falseis a cheap way to try it first.🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is enabled.