Repository navigation
Math-#335: c2-torus omission controls require intended MISMATCH reason (Draft; merge HOLD for Dylan workflow OK) - #562
Draft
d6g8k5htny-coder wants to merge 1 commit into
Draft
d6g8k5htny-coder wants to merge 1 commit into
d6g8k5htny-coder wants to merge 1 commit into
Conversation
The replay job treated any exit code 1 as a passed omission control. Each mutant now passes only when it exits 1, stdout contains "MISMATCH against RESULTS.json", and stderr is empty. Any other status prints that mutant's separate stdout and stderr and fails the job. Co-authored-by: Dylan Roy <d6g8k5htny-coder@users.noreply.github.com>
This was referenced Nov 17, 2026
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.
Math-#335 — omission controls must carry the MISMATCH reason
Draft. Merge HOLD until Dylan OKs this
.github/workflows/change. Do not mark Ready. Engineering only. This does not change checkers, proofs,RESULTS.json, manifests, ortransfer.py, and it does not claim scientific acceptance.Base:
dee08f4f4c984bfac0ee4ff289c87c677efb5ec9Head:
6bd4fae46575c068af58b80a3ba13ba2105ffae4Workflow blob:
e8c11afdc19eba9e9090aa7dca8ab130e411c833→9886f17ef75729f4ffafc48c10bcc50839e32ff7Unchanged
transfer.pyblob:05dc3fba1d1f1399519569f113911ed043a67fbaCharacterization
Local interpreter: CPython 3.12.3 (
/usr/bin/python3). The workflow pins hosted CPython 3.11.16; that pin is not installed here. Commands match the job:PYTHONDONTWRITEBYTECODE=1, packet directory,-B -S(normal) and-B -O -S(optimized), stdout and stderr kept separate. The workflow's manifest/pin/copy step printedmanifest, pins and copies verified(rc 0, empty stderr).No mutant failed through
require()/AssertionError. Each genuine mutant exited 1 with stdout exactlyMISMATCH against RESULTS.json\n(30 bytes, SHA-256800a127a1a5fc450d536fddc71c7c47884d283a798f08c885f782544f37452d9) and empty stderr (SHA-256e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855). Normal and optimized streams were byte-identical. The fixed literal in the workflow is that driver line.transfer.py --checkcheck passedtransfer.py --checkcheck passedcontrols.pycontrols: 0 failurescontrols.pycontrols: 0 failures--mutant no-imageMISMATCH against RESULTS.json--mutant no-imageMISMATCH against RESULTS.json--mutant no-thetaMISMATCH against RESULTS.json--mutant no-thetaMISMATCH against RESULTS.json--mutant drop-ratioMISMATCH against RESULTS.json--mutant drop-ratioMISMATCH against RESULTS.json--mutant eta-halfMISMATCH against RESULTS.json--mutant eta-halfMISMATCH against RESULTS.json--mutant fp-constMISMATCH against RESULTS.json--mutant fp-constMISMATCH against RESULTS.jsoncontrols.pystdout was 1789 bytes, SHA-25690247407c99f551e4d2c7eda56602b408b4fe11fbacde3f1f92b215f5de0eeed, same in both modes.--checkstdout SHA-256c6b9ef18c4dcb1476b486467d448ef6967aa414837cfa1c6c512598965191045.Repair
.github/workflows/c2-torus-transfer.ymlonly. Each omission control is accepted only whenrcis 1, stdout contains the fixed literalMISMATCH against RESULTS.json, the stderr file exists, and stderr is empty. Any other exit 1, exit 0, or other status fails the job and prints that mutant's stdout and stderr. Stdout and stderr are separate files (/tmp/mutant_$m.stdout,/tmp/mutant_$m.stderr).Matcher evidence (VM, not committed)
The acceptance loop was extracted from this workflow and run against the captured genuine streams and against real short-lived Python processes that wrote the adverse streams. 27/27 rows matched. Genuine normal and genuine optimized accepted all five mutants (exit 0). Each adverse case was applied to each of the five mutant slots while the other four stayed genuine; every one exited 1 and printed that slot's logs.
RuntimeError: unrelated crash, rc 1, traceback on stderrWRONG REASON, rc 1, empty stderrSample failure text for
no-image:mutant no-image not rejected for the intended reason (rc=1)then stderrRuntimeError: unrelated crash(rc=1)with empty stdout and stderr sections(rc=1)and stdoutWRONG REASON(rc=0)and stdoutMISMATCH against RESULTS.json(rc=2)and stdoutMISMATCH against RESULTS.jsonLimits
Scientific effect NONE. No theorem, proof, axiom, or
RESULTS.jsondisposition. Hosted 3.11.16 was not the interpreter for this characterization. The probe feeds streams to the acceptance loop; it is not a hosted Actions run.Grok Bot agent 7 (Grok Bot support agent; non-Claude, nonauthor lane) · credit 0 · sci NONE · OBL OPEN · engineering only, math fail-closed