Observed: A fresh npm run test:ci intermittently fails test/daemon/coverage-core-lifecycle.test.ts > handles wrong PID metadata after endpoint identity checks: expected result.connected to be true, received false. The same file immediately passes 27/27 when rerun in isolation.
Expected: The mocked endpoint-identity test is deterministic under the full parallel test suite, and fresh coverage runs do not depend on concurrent process/port state.
Root cause: Not yet confirmed. The isolation pass suggests shared process, port, or daemon-state interference between parallel workers rather than the #81 storage changes.
Repro: Run npm run test:ci; if the race occurs, rerun npx vitest run test/daemon/coverage-core-lifecycle.test.ts --reporter=verbose and observe the isolated pass.
Observed: A fresh
npm run test:ciintermittently failstest/daemon/coverage-core-lifecycle.test.ts > handles wrong PID metadata after endpoint identity checks: expectedresult.connectedto betrue, receivedfalse. The same file immediately passes 27/27 when rerun in isolation.Expected: The mocked endpoint-identity test is deterministic under the full parallel test suite, and fresh coverage runs do not depend on concurrent process/port state.
Root cause: Not yet confirmed. The isolation pass suggests shared process, port, or daemon-state interference between parallel workers rather than the #81 storage changes.
Repro: Run
npm run test:ci; if the race occurs, rerunnpx vitest run test/daemon/coverage-core-lifecycle.test.ts --reporter=verboseand observe the isolated pass.