Repository navigation
Conversation
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.
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
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
verify_multitarget.pyscored 0 killed of 7, and its survivor lines are identical in shape toverify_emit_bitexact.py's (#2538): the gate's ownsys.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 reachmain().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_refreads the Python model while C and Rust come fromt27c. Perturbingpy_refmakes 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_bitexactplant work, and the reason both are one-line edits in a specific place rather than "break something".Result
Only boundary survivors remain in both — lines 40 and 81 here, which are plumbing rather than verdicts.
Refs #2492