Skip to content

Master FROZEN_HASH is stale: every PR fails Verilog widths and parse-ratchet #14108

Open

Description

@gHashTag

Boundary

  • bootstrap/stage0/FROZEN_HASH

User Scenarios

A contributor opens a PR that does not touch bootstrap/src/compiler.rs (for example PR #14107, one .t27 file). The checks "Verilog widths (absurd-width ledger)" and "parse-ratchet" still fail with t27c FROZEN HASH violation, because master's own seal is stale: at master head de792b0 the seal file starts 0d9aa03b788a, while sha256 of compiler.rs starts 02802d4b3f60. Every PR inherits these two reds.

Requirements

  • FR-001 MUST make bootstrap/stage0/FROZEN_HASH on master match sha256 of master's bootstrap/src/compiler.rs, written with the freeze ceremony (FROZEN.md section 5), on a master-built t27c.
  • FR-002 MUST NOT change bootstrap/src/compiler.rs in the same PR.

Success Criteria

  • On a PR that does not touch compiler.rs, "Verilog widths (absurd-width ledger)" and "parse-ratchet" no longer report a FROZEN HASH violation.
  • Negative control: changing one byte of compiler.rs without a reseal still fails both checks.

Refs #14107, #5928

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions