Repository navigation
seal(t27f): re-seal frontend.t27, stale since 3b7c34bf1 (#10939), Seal Coverage green again (Closes #10967) - #10968
Merged
Merged
Conversation
…#10967) 3b7c34b (#10939) changed specs/t27f/frontend.t27 without re-sealing it, so the Seal Coverage check failed on every pull request. Re-sealed on the Railway lab with a compiler built from f9fe37a. Verify prints all hashes MATCH, and the coverage check reports 2796 holding, 113 baselined, none newly broken. The spec is untouched. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Contributor
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
1 participant
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.
Closes #10967.
Why. 3b7c34b (#10939) changed
specs/t27f/frontend.t27without re-sealing it, so.trinity/seals/t27f_T27fFrontend.jsonwent[stale]and the Seal Coverage check (coverage) fails on every PR, #10958 among them. Same cause as #10814.What. The seal file was regenerated by
t27c seal specs/t27f/frontend.t27 --saveon the Railway lab, with a t27c built from master f9fe37a and zig on PATH, then copied back by base64 with a sha256 check (4a1c0e23...). Nothing was edited by hand. The diff is that one file; the spec is untouched.Verified (on the lab).
t27c seal --verify specs/t27f/frontend.t27reported MISMATCH on the zig, verilog, c and rust gen hashes.all hashes MATCH; the seal records tests 9/9 pass.tools/check_seal_coverage.py: 2909 seals, 2796 hold, 113 known-broken listed in seal_baseline.txt, none newly broken.🤖 Generated with Claude Code