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
determinism: a daemon pause that cannot engage gives different traces across runs (intermittent, added by #73) #105
The determinism unit determinism: constructed history: a daemon pause that cannot engage (added to main by #73) is intermittent. Two runs of one history recorded different traces at observation 4 (incremental). It passed on one run and failed on another for the same commit (4bc4eb1, PR #90). It also failed on main (4d3c8a9) before the stream-order fix, at observation 0 (cli).
PR #90 excludes it from PR CI until this is fixed, so the determinism job is not red at random.
Replay
cd packages/oracles && pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "determinism: constructed history: a daemon pause that cannot engage"
The failure message prints the history and the first 2,000 characters of each run's trace. For the full texts, a scratch patch to src/oracle-property.ts that prints them was needed (see #81).
Authority
Register (2026-11-14, determinism under load): an oracle driver must not rely on wall-clock ordering. A daemon pause that depends on timing is that kind of dependency.
Activity
fix(oracles): exclude the intermittent daemon-pause unit (#105); gate…