Commit 0a5f096
committed
gate: assert ARM64 gate binary identity (mirror x86_64 BINARY_MATCH)
Symmetric defense to e808676 — guards against any future ARM64
build-pipeline refactor (e.g., switching to cp-and-cache for build
speed) silently regressing the binary-identity property.
Today the ARM64 chain (cmake clean → fetch → checkout → build → test
in same repo) inherently couples binary identity to checked-out
commit, so the check is belt-and-suspenders. Per theologian
2026-04-22 00:47:10Z: the defense-in-depth value is in preventing
future regression of the safety property, not in catching today's
bugs.
After build_phoenix.sh + chmod +x python:
- capture sys.version of the freshly-built binary
- grep for $ARM64_COMMIT (the just-checked-out short hash)
- exit 99 if absent, with explicit ARM64_BINARY_MISMATCH message
Existing 'ARM64_REMOTE_FAIL' cascade catches the non-zero exit and
fails the gate. Transcript carries verbatim ARM64_BINARY_MATCH or
ARM64_BINARY_MISMATCH for gatekeeper item python#11 verification.1 parent e808676 commit 0a5f096
1 file changed
Lines changed: 9 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
534 | 534 | | |
535 | 535 | | |
536 | 536 | | |
| 537 | + | |
| 538 | + | |
| 539 | + | |
| 540 | + | |
| 541 | + | |
| 542 | + | |
| 543 | + | |
| 544 | + | |
| 545 | + | |
537 | 546 | | |
538 | 547 | | |
539 | 548 | | |
| |||
0 commit comments