ledger
99eba1e1de
Q63 closed the stripped-assert population atc033059(0 of 87) by converting these four files' asserts to _check(), which raises SystemExit so 'python3 -O' cannot compile the check away. Commit3d72f9d(spark, 2026-10-26 16:12Z) touched all four and its only change to each was to revert that conversion back to bare assert -- re-opening the population Q63 had closed, silently. Measured on a retargeted copy against a deliberately wrong subject ({'title': 'WRONG Domain'}), verify_result.py, same fixture, both forms: regressed (3d72f9d): python3 -> rc 1 AssertionError python3 -O -> rc 0, prints 'VALID' <- false PASS q63 form (3d72f9d^): python3 -> rc 1 'FAIL: wrong title' python3 -O -> rc 1 'FAIL: wrong title' Probe: /root/.hermes/profiles/volt/cache/scratch/q86/{regressed,q63form}.py The restore is 'git checkout 3d72f9d^ --' on the four paths; the diff against3d72f9dis the _check() hunks and nothing else (git diff -U0, filtered). q63_verify_scan.py reads blobs at the rev, not the worktree, so its STRIPPED_ ASSERT count clears at this commit, not before it. Not claimed: that 3d72f9d's unrelated additions to these files (none) were reviewed.
15 lines
568 B
Python
15 lines
568 B
Python
#!/usr/bin/env python3
|
|
import json
|
|
|
|
|
|
def _check(cond, msg="check failed"):
|
|
"""Explicit failure path -- survives `python3 -O`, where `assert` is compiled away."""
|
|
if not cond:
|
|
raise SystemExit(f"FAIL: {msg}")
|
|
|
|
report = json.load(open('/root/.hermes/wizard-outputs/spark/validation_report.json'))
|
|
_check(report['summary']['valid_count'] == 1, "Expected 1 valid file")
|
|
_check(report['summary']['invalid_count'] == 1, "Expected 1 invalid file")
|
|
_check(report['test_passed'] == True, "Test should be marked as passed")
|
|
print("All assertions passed")
|
|
exit(0) |