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: setupThrows: a stopped run exits SIGABRT but its done line says completed (seed -1659558018), on main too #117
The random unit random seed: a declaration fault: setupThrows found a greppable-stream counterexample on seed -1659558018 (path 0:0:0:0:0:0:0) in the random shard 3/3 of PR #90's seed measurement (run 43778881284). The stopped run exits with SIGABRT, but its last line is oracle-gaps: done completed, 4 gaps (provisional), report <package>/out-stop/summary.md, not done error.
It reproduces on origin/main (4d3c8a9): the replay job replay -1659558018 setupThrows in run 43782377713 fails with the same difference. Filed under P4.
Replay
cd packages/oracles && ORACLE_SEED=-1659558018 ORACLE_PATH=0:0:0:0:0:0:0 ORACLE_PROPERTY=oracle-gaps.report ORACLE_UNIT='random seed: a declaration fault: setupThrows' pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "^oracle-gaps\.report(?: | > )random seed: a declaration fault: setupThrows$"
#115 changes how the stdout gap lines are judged against results.json. It does not mention the stop path, the SIGABRT exit, or the done line of a stopped run. The stop law (law 13 in the e2e oracle) is not in #115's list. So this is not covered there, and it is not #99 (which is about wall-clock cuts), so I filed it here.
Activity