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
packages/core/test/process/process.test.ts is flaky on a loaded machine. The two AppProcess interruption tests ("fiber interruption cleans up the scoped child process after readiness" and the timeout variant) sometimes fail with:
The child script writes the ready file before registering its SIGTERM handler, and writeFileSync creates the file empty before writing the pid. So the test can read an empty file, or send SIGTERM before the handler exists (the child then dies without writing settled).
OpenCode version
dev
Steps to reproduce
cd packages/core
Run bun test test/process/process.test.ts 16 times in parallel, in a loop (I used ~60 rounds).
A few runs fail as above; running the file alone rarely shows it.
Related to #37321 but not a duplicate. Besides the empty-read symptom, the child writes ready before registering its SIGTERM handler, so the test can signal it before the handler exists and settled is never written. #48205 only makes waitForFile tolerate empty files; #51952 fixes both at the source (handler first, atomic write via rename).
Activity
github-actions commentedon Sep 28, 2026
This issue might be a duplicate of existing issues. Please check:
saulalfonsos commentedon Oct 5, 2026
Related to #37321 but not a duplicate. Besides the empty-read symptom, the child writes
readybefore registering its SIGTERM handler, so the test can signal it before the handler exists andsettledis never written. #48205 only makeswaitForFiletolerate empty files; #51952 fixes both at the source (handler first, atomic write via rename).