The property test's execFileSync timeout (5000ms) was identical to the scanner's own internal stdin-timeout (hooks/gsd-read-injection-scanner.js:109, also 5000ms). Under concurrent test-chunk load on linux-node22 — which #2089's 3 new cursor test files redistribute — the scanner subprocess's stdin 'end' event can fire late enough that execFileSync's SIGTERM arrives before the scanner's own process.exit(0), producing err.status=null → exitCode=1 → spurious property-test failure. The scanner has no process.exit(N!=0) paths; the only non-zero exit is from the signal-kill race. Doubling the test ceiling to 10000ms gives the scanner's 5000ms internal exit a 5s buffer to win the race deterministically on every node version.
4.6 KiB
4.6 KiB