Skip to content

tests: a missing input skips loudly instead of failing into a baseline (Refs #2161) - #2739

Merged
gHashTag merged 3 commits into
masterfrom
w699-loudskip
Aug 27, 2026
Merged

tests: a missing input skips loudly instead of failing into a baseline (Refs #2161)#2739
gHashTag merged 3 commits into
masterfrom
w699-loudskip

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

specs/scratch/ is gitignored — 578 MB of generated benchmark drafts, re-derivable from the 343 committed scripts/gen_w<NNN>.py generators. So in a fresh clone this whole target panicked on read_dir, and the failure was then recorded in the CI baseline as known failing: 358 tests, 15% of the suite, disabled by a .gitignore line and made invisible by a ledger.

A missing input is not a failing test. It is also not a passing one — which is why the guard prints rather than returning quietly. A silent skip is how the count reached 358 in the first place. Each skip names the test, the directory, and how to restore it.

failing skipping
before 358 0
after 1 357

That one is the point. corpus_classifier_matches_lean_completeness fails on a real disagreement — specs/api/tri_net_api.t27, where the Rust classifier says not-lowerable and the Lean theorem says lowerable — and it fails identically before and after this change, checked by stashing.

It was the only true failure in the target, and it sat among 357 false ones. The baseline recorded all 358 as the same thing, which is what a ledger does to a population it cannot distinguish: it makes the one that matters cost exactly as much attention as the 357 that do not.

Nothing here regenerates the witnesses — 578 MB does not belong in a test run. When they are present the 357 run as before.

Refs #2161

…e (Refs #2161)

`specs/scratch/` is gitignored -- 578 MB of generated benchmark drafts,
re-derivable from the 343 committed `scripts/gen_w<NNN>.py` generators.
So in a fresh clone this whole target panicked on `read_dir`, and the
failure was then recorded in the CI baseline as "known failing": 358
tests, 15% of the suite, disabled by a .gitignore line and made invisible
by a ledger.

A missing INPUT is not a failing test. It is also not a passing one,
which is why the guard PRINTS rather than returning quietly -- a silent
skip is how the count reached 358 in the first place. Each skip names the
test, the directory, and how to restore it.

    before   358 failing, all of them for the same absent directory
    after    357 skipping loudly, 1 failing

That one is the point. `corpus_classifier_matches_lean_completeness`
fails on a real disagreement -- specs/api/tri_net_api.t27, Rust says not
lowerable and the Lean theorem says lowerable -- and it fails identically
before and after this change, checked. It was the only true failure in
the target and it sat among 357 false ones, in a baseline that recorded
all 358 as the same thing.

Nothing here regenerates the witnesses: 578 MB does not belong in a test
run. When they are present the 357 run as before.
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-27 20:21:28 UTC

Summary

Status Count
Total Open PRs 8
PRs with Failing Checks 7
PRs with All Checks Green 1
READY 0
FAILING 7
PENDING 0

Seal Status

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

@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-27 20:48:50 UTC

Summary

Status Count
Total Open PRs 8
PRs with Failing Checks 7
PRs with All Checks Green 1
READY 0
FAILING 7
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=f9074870f5f3 != 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 a19ccce into master Aug 27, 2026
32 of 33 checks passed
@gHashTag
gHashTag deleted the w699-loudskip branch August 27, 2026 20:59
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