Skip to content

t27b ledger: re-measure at master 7552b89d0 -- 180 new specs listed, max_not_pass 75 -> 134 (Closes #10465) - #10473

Merged
gHashTag merged 2 commits into
masterfrom
ledger-refresh-10416b
Oct 18, 2026
Merged

gHashTag merged 2 commits into
masterfrom
ledger-refresh-10416b

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #10465.

#10445 was squash-merged at 89254d2 with the t27b ledger master already carried (max_not_pass 75, 177 specs unlisted): the merge happened before the ledger was re-measured at that tip, so t27b-native-ratchet stayed red on master. The corpus ledger needs nothing: the Corpus Ratchet reports RATCHET: CLEAN at 7552b89.

What changed

Only docs/reports/t27b_expectations.json, written by the ratchet's own bless command with --accept-new, never by hand.

  • Measured at master 7552b89: a full corpus run on the Railway lab (aarch64 t27b under qemu, reference t27c with a warm cache), 240 s per-spec timeout. An earlier run at 60 s timed out specs/t27f/spec_graph_export.t27 under lab load (load average ~65); it passes alone in 4.6 s, which is why the timeout is longer here.
  • 180 specs added to the ledger: 121 pass, 59 blocked.
  • max_not_pass 75 -> 134, exactly the 59 newly blocked entries (133 blocked + 1 codegen in total). The cap moves for no other reason.
  • No existing entry moved; no unexpected pass or failure.

Check

The ratchet against the fresh run after the bless: green, UNLISTED 0, UNEXPECTED FAILURE 0, UNEXPECTED PASS 0, OVER CAP 0.

🤖 Generated with Claude Code

gHashTag and others added 2 commits October 18, 2026 20:25
…sted, max_not_pass 75 -> 134 (Closes #10465)

#10445 squash-merged with the t27b ledger master already carried, so t27b-native-ratchet
stayed red (UNLISTED 177). Same measurement, taken at 7552b89: a full t27b sweep on the
Railway lab with a 240 s timeout so load cannot time a spec out, blessed with --accept-new,
plain ratchet re-run green. 180 specs added: 121 pass, 59 blocked; the cap follows the
not-pass count.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…m master, to be re-blessed on the lab (Refs #10465)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-18 13:39:43 UTC

Summary

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=fad12492937a != 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).

@gHashTag
gHashTag enabled auto-merge (squash) October 18, 2026 13:52
@gHashTag
gHashTag merged commit a7e6bf2 into master Oct 18, 2026
27 of 29 checks passed
gHashTag added a commit that referenced this pull request Oct 18, 2026
…7b ledger from #10473

Master's ledger (re-measured at 7552b89) still lists this branch's specs as master had them.
The resolution keeps master's ledger and records what this branch changes:
- reel_marketing.t27 is new and passes;
- token_floor_scenes.t27 now calls @sin (the hover), and token_floor_mux.t27 uses it, so both are
  blocked on ExprCall(@sin), unimplemented, as CI's run of the merge head measured;
- max_not_pass 130 -> 132 for those two.

Refs #10469

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

t27b ledger: re-measure at master after #10445 merged with a stale ledger

1 participant