Skip to content

fix(gates): verify_multitarget killed 0 of 7 — the same mistake, twice (#2492) - #2541

Closed
gHashTag wants to merge 3 commits into
masterfrom
fix/multitarget-verdict
Closed

gHashTag wants to merge 3 commits into
masterfrom
fix/multitarget-verdict

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

verify_multitarget.py scored 0 killed of 7, and its survivor lines are identical in shape to verify_emit_bitexact.py's (#2538): the gate's own sys.exit(0 if ok else 1) under both return operators, and all three comparison FAIL branches under inversion.

Both controls cover the skip pair. Both leave through skip() and never reach main().

Two gates, one mistake, and I made it twice — the second time three iterations after writing down the first. That is what a class looks like when you have not internalised it: the rule was recorded, the next control was written the same way, and only a measurement caught it.

The plant moves one arm

py_ref reads the Python model while C and Rust come from t27c. Perturbing py_ref makes the model disagree with backends that are unchanged — a real cross-target divergence. Perturbing the spec or the emitter would move every arm together and plant nothing.

That is the same distinction that made the verify_emit_bitexact plant work, and the reason both are one-line edits in a specific place rather than "break something".

Result

verify_emit_bitexact.py   0/17  ->  13/17
verify_multitarget.py      0/7  ->   5/7

Only boundary survivors remain in both — lines 40 and 81 here, which are plumbing rather than verdicts.

Refs #2492

The pull request opened with 7 checks where a sibling opened minutes
earlier got 35. tools/verify_multitarget.py is explicitly listed in
emit-bitexact-gate.yml's pull_request paths and that gate did not run.

Not diagnosed, only observed: an empty commit is the cheapest way to ask
whether the trigger or the run was the thing that went missing.
@gHashTag

Copy link
Copy Markdown
Collaborator Author

Re-opened as a fresh pull request: this one received 7 checks where a sibling opened minutes earlier received 35, and emit-bitexact never ran despite the changed file being listed in its paths. An empty commit did not re-trigger it. Not diagnosed; re-opened rather than merged without checks.

@gHashTag gHashTag closed this Aug 23, 2026
gHashTag added a commit that referenced this pull request Aug 23, 2026
Re-opened from #2541, whose pull request received 7 checks where a
sibling opened minutes earlier received 35 -- emit-bitexact did not run
despite tools/verify_multitarget.py being explicitly listed in its
pull_request paths. An empty commit did not re-trigger it, and a second
branch touching the SAME files got a normal check list, so the cause was
that pull request rather than the paths.

Not diagnosed. Re-opened rather than merged without checks.
@gHashTag
gHashTag deleted the fix/multitarget-verdict branch October 26, 2026 06:10
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