You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
random seed: an ambiguous authored mutant: field-drop judged not-distinguished, owed indeterminate (seed 333199054), on main too #116
The random unit random seed: an ambiguous authored mutant found a classification counterexample on seed 333199054 (path 0:0:0:0:0:0:0) in the random shard 1/3 of PR #90's seed measurement (run 43778881284). The CLI reports src/sut.ts:D_OBJ:30:field-drop#0 as not-distinguished, and the model owes indeterminate.
It reproduces with the same seed and path on origin/main (4d3c8a9): the replay job replay 333199054 an ambiguous authored mutant in run 43782377713 fails with the same difference. So it is a base defect, not caused by PR #90. Filed under P4.
Replay
cd packages/oracles && ORACLE_SEED=333199054 ORACLE_PATH=0:0:0:0:0:0:0 ORACLE_PROPERTY=oracle-gaps.report ORACLE_UNIT='random seed: an ambiguous authored mutant' pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "^oracle-gaps\.report(?: | > )random seed: an ambiguous authored mutant$"
#115 (stream law) and #99 (wall-clock cut) do not name field-drop or indeterminate, and #99 has no mention of the indeterminate outcome. The cause is not established. It may be a timing cut that gives indeterminate on one side only, but that is a guess until the trace is read.
Activity