Skip to content

seals: ml_host_io_model gen_hash_verilog follows the gen-verilog assignment-target fix (Closes #11102) - #11105

Merged
gHashTag merged 1 commit into
masterfrom
lane/seal-ml-host-io-11102
Oct 19, 2026
Merged

gHashTag merged 1 commit into
masterfrom
lane/seal-ml-host-io-11102

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #11102

Master is red on coverage and spec-guards since #11094 (gen-verilog stopped wrapping an assignment target in $signed): the seal of specs/ml/host_io_model.t27 still held the old gen_hash_verilog. The spec did not move, so this PR changes one hash in one seal.

Why a one-value edit and not t27c seal --save: on macOS the spec does not compile under Zig (a bare literal passed to the variadic libc open, filed as #11103), and seal --save refuses to overwrite a recorded pass with a blocked run, correctly. The seal keeps its recorded 3 of 3 passed because the tests ran on Zig whose hash is unchanged: gen_hash_zig, gen_hash_c and gen_hash_rust still MATCH.

The new value is what t27c computes: a8beaecd9847f48f06d18bd018afaed19333a16133ee88f74d5e9720df8bab5d, the same prefix the CI job printed as current=a8beaecd9847.

Checks run before the commit, with t27c built from master: t27c seal specs/ml/host_io_model.t27 --verify (no MISMATCH), python3 tools/check_seal_currency.py (exit 0). The diff is one line in .trinity/seals/ml_host_io_model.json.

🤖 Generated with Claude Code

…gnment-target fix (Closes #11102)

specs/ml/host_io_model.t27 is unchanged and gen_hash_zig, gen_hash_c, gen_hash_rust still MATCH; only the Verilog hash moved (#11094). t27c seal --save refuses on macOS for this spec (#11103), so the one value was set to what t27c computes; the recorded 3 of 3 test pass stays valid because the Zig it ran is byte-identical. t27c seal --verify prints no MISMATCH and tools/check_seal_currency.py exits 0.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@gHashTag
gHashTag enabled auto-merge (squash) October 19, 2026 17:20
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-19 17:20:34 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 47
PRs with All Checks Green 3
READY 2
FAILING 47
PENDING 0
NO CHECKS YET 0

These columns do not partition: 2 + 47 + 0 + 0 = 49, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=e34e1b174c96 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

seals: ml_host_io_model gen_hash_verilog is stale after the gen-verilog assignment-target fix; coverage and spec-guards are red on master

2 participants