fix(ci): the corpus ledger says what is true - #5551
Merged
Merged
Conversation
The corpus ratchet had not run on CI since earlier Corpus Ratchet steps went red. On master 769f325 it reports 68 unexpected failures, 57 unexpected passes and 7 worsened discard counts, against 151 entries at a cap of 152. - 51 entries whose specs now pass every phase are removed. - 6 specs that parse now and fail one phase later are re-keyed to that phase, keeping their old reason (composition, multi_head_attn, pins/parser, packed_trit, jit_semantics, packed_vsa). - 5 discard pins that improved move down (uart, coder/benchmark, cordic, jit, lotus). - 33 failures of ported specs merged while the gate was red are added under #5549, whose ports are to be redone. 151 -> 133 entries; the cap follows the count down to 133. Not ledgered, on purpose: 29 core specs that began discarding tokens after edits since 2026-09-12, and 7 whose discard counts rose. Those are repairs, not records; the ratchet now reports exactly them. Refs #5497 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
This was referenced Oct 2, 2026
Closed
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.
What
The last step of Corpus Ratchet,
t27c suite --ratchet --corpus-only, had not been reached on CI since the earlier steps went red (they are green since #5502 and #5504). On master 769f325 it reports:Change to docs/reports/suite_expectations.json
parse->verilog-no-keyword-decl/parse-no-discard/typecheck; old reason kept, prefixed with the movemax_entries_why_entries_fellrecords the same breakdown.Not ledgered, on purpose
given/when/thentest blocks, so the parser now throws the whole block away (bdd-block-fallback); others leavetop-level-resyncorbrace-bodydebris.These are repairs, not records; they come in the next PRs. With this ledger the ratchet reports exactly them: 29 unexpected failures, 7 worsened, 0 unexpected passes, 0 expired.
Refs #5497
🤖 Generated with Claude Code