Skip to content

fix(t27b fuzz): FuzzRng, not Rng; bless the shell census (Refs #6442) - #6879

Merged
gHashTag merged 1 commit into
masterfrom
sieve/t27b-fuzz-fix
Oct 6, 2026
Merged

gHashTag merged 1 commit into
masterfrom
sieve/t27b-fuzz-fix

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 6, 2026

Copy link
Copy Markdown
Owner

Refs #6442
Refs #6488 #6063

Why

#6848 auto-merged at 41dcb34 before this commit reached it. That merge moved two gates on master, and both are red until this lands:

  • Corpus ratchet (type names): specs/tri/t27b/fuzz.t27 declared struct Rng, which specs/tri/utils/random.t27 already owns, so Rng became a new conflicted type (ledger 84, observed 85).
  • cli-tri tri census pin --gate: the new loop-tools-gate step "tri t27b fuzz generates and judges in t27" moved the shell census.
    • run: steps went from 291 to 292.
    • the runner does went from 270 to 271.

What

  • Rename: Rng is now FuzzRng in specs/tri/t27b/fuzz.t27, and gen/c/tri/t27b/fuzz.c is regenerated; only the name changes.
    • tri t27b gen-check on the t27c lab returned SAME 318c551bfbd2.
    • tri types ratchet returns RATCHET: CLEAN.
  • Census: tools/census/shell.txt is re-recorded. The only lines that moved are the two above. The fetches and quiet censuses did not move, and tri census pin --gate returns PASS.
  • Behaviour: none changes. Every committed fixture still renders byte-identically, and scripts/ci/test_the_t27b_fuzz_judges_in_t27.py reports 0 failures.

Foreign files

None touched.

🤖 Generated with Claude Code

Two CI gates the first push moved:

- corpus ratchet (type names): specs/tri/t27b/fuzz.t27 declared `struct Rng`,
  and specs/tri/utils/random.t27 already owns that name, so Rng became a new
  conflicted type (ledger 84, observed 85). Renamed to FuzzRng; gen-c
  regenerated, only the name changes in it, and `tri t27b gen-check` on the
  t27c lab says SAME 318c551bfbd2. `tri types ratchet`: CLEAN.
- shell census: `run: steps` 291 -> 292 and `the runner does` 270 -> 271,
  both from the one new step "tri t27b fuzz generates and judges in t27" in
  loop-tools-gate.yml. tools/census/shell.txt re-recorded; fetches and quiet
  did not move.

Refs #6442

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

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-06 14:30:01 UTC

Summary

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

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

Seal Status

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

This was referenced Oct 6, 2026
@gHashTag
gHashTag merged commit 6fab1e1 into master Oct 6, 2026
22 of 28 checks passed
gHashTag added a commit that referenced this pull request Oct 6, 2026
…#6442) (#6924)

Two things on master that #6879 did not cover:

- quiet census (cli-tri `tri census pin --gate`): "named a path but not
  quiet" 159 -> 160. `tri census explain` puts it on one file alone,
  .github/workflows/queen-export-push.yml from #6847: its new env line
  `GH_TOKEN: ${{ secrets.GH_AGENT_TOKEN || github.token }}` (line 66) is
  one more excluded, non-quiet line; the two lines below it only shifted
  by three. tools/census/quiet.txt re-recorded with `tri census pin
  --bless`; fetches and shell did not move.
- specs/isa/t27a_mnemonics.t27 (#6765) had no saved seal. Sealed on the
  t27c lab with zig on PATH (`PATH=/opt/zig:$PATH t27c seal --save`):
  tests 5/5 pass, `seal --verify` all hashes MATCH, `tri seals
  sync-twins` wrote nothing, check_seal_coverage OK 1331 hold.

Refs #6507
Refs #6488

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.

1 participant