Repository navigation
Use a pinned ARM engine recipe in normal CI - #200
Merged
Merged
Conversation
5 of 10 tasks
This was referenced Oct 2, 2026
Contributor
Author
|
This producer is now in develop through PR #133's normal merge |
This was referenced Oct 7, 2026
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.
PR #133, #136 and #153 now use a pinned ARM engine built in their current CI run. This replaces the expiring standalone artifact from #73. The native ARM job uses the existing pinned llama.cpp recipe and Ubuntu container, validates the archive, and requires a real SmolLM2 reply when it builds. An exact recipe-hash cache avoids repeated builds; only pushes to develop can save it.
All three consumers inherit the same producer change, retain their Ubuntu 22.04 ARM runner and established check name, and verify archive SHA-256
a92e404708feae91cbede43322e445971450de8a204f4ff51502a7f42f5df8b8. Their existing component records use size6665019. The archive keeps the engine, dependencies and licences; changing checkout provenance stays outside the reproducible archive.Validation: the native build in run 36961744562 passed architecture/library checks and a real reply. Its original pin check refused the new canonical archive, as intended. Independent inspection verified the digest, 40 safe members, eight ARM64 ELF files, dependency limits and receipts. Eleven policy tests, archive refusal fixtures, all four basic gates and one independent development review passed. Candidate
430e36448835a4a03e57a5c778cebba32240067d, treef89116384e5f02ae90157da7e1abe835b5ade699, includes the verified pin and checkout receipt fix; run 36964376212 is its current CI gate.This draft targets develop for #97 and replaces #73. Current CI and an operator-posted different-family adversarial PASS remain required before merge. The prepared 2 October Jetson attempt remains a separate hardware proof with its fixed inputs.