Skip to content

seals: refresh the 7 seals the R6 splice changed (Refs #12664) - #12812

Merged
gHashTag merged 1 commit into
masterfrom
lane/seals-r6
Oct 27, 2026
Merged

gHashTag merged 1 commit into
masterfrom
lane/seals-r6

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

Coverage run 40466252523 named 72 stale-gen seals after #12804 (the use-scope fix): a name that used to be refused as ambiguous now splices from the module its import line named, so those specs' gen_rust changed. 7 resealed with this tree's own compiler (spec tests pass); the other 65 refuse to seal on the known gen-rust lifetime defect (#11182 family: bus/config/ml -- 'a []T field filled from borrowed storage'), unchanged, each already tracked. Seals only; no spec, no foreign line.

The use-scope fix makes previously-refused names splice, so 7 specs'
gen_rust changed and their seals went stale (coverage run 40466252523
named 72; 65 of them refuse to seal on the known gen-rust lifetime
defect #11182 -- bus/config/ml family, each already its own defect;
they stay on the record unchanged).
@gHashTag
gHashTag enabled auto-merge (squash) October 27, 2026 07:30
@tri-claw

tri-claw Bot commented Oct 27, 2026

Copy link
Copy Markdown

Summary by t27-bees

This PR refreshes 7 seal files after the R6 splice change (#12804) altered how ambiguous names resolve, causing generated code hashes and spec hashes to update. All 7 seals now pass their spec tests with the current compiler.

Worth a look

  • .trinity/seals/blog_BlogEpicProgress.json: Test count increased from 3 to 4 with vacuous tests dropping from 3 to 0 — suggests the splice change made previously-ambiguous tests concrete and runnable.
  • .trinity/seals/t27os_T27osRouter.json: Test count increased from 7 to 8 — similar implication that a previously-skipped test now executes.
  • .trinity/seals/theory_CompilerTheoryToolchain.json: Test count increased from 20 to 21 — same pattern; verify the new test is intentional coverage, not a flaky pass.
  • All 7 files: spec_hash changed in every seal — confirms the specs themselves (or their transitive closure) were re-evaluated; ensure no spec source files were accidentally modified (the PR claims "no spec, no foreign line").
  • All 7 files: built_by and test_runner now identical across seals — expected for a single reseal run, but confirms the bootstrap compiler and test runner are consistent.

Read: 7 files, +63 -62, the whole diff. Head bdd0107. Model: openai-compatible/nvidia/nemotron-3-ultra-550b-a55b. Commands: @t27-bees review | summary | help | pause | resume. Free for every repository.

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-27 07:34:28 UTC

Summary

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

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=67adcf31aff7 != 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 merged commit ced2e0b into master Oct 27, 2026
26 of 32 checks passed
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