#238 document-stream-postgres can hang in CI
–
- github
- github/openchronology/timeline-app
- github/openchronology/timeline-app#238
- issue
- state:closed
On PR #237's run (https://github.com/openchronology/timeline-app/actions/runs/39361668254), the job **PostgreSQL 16 / native pgmp / accounts and sharing** sat in \`node test/document-stream-postgres.mjs\` for over two hours with no output, until it was cancelled. The same job on the same commit's push run passed in about 12 minutes, so the hang is intermittent. PR #237 only changes the browser UI, so it didn't cause this. The test printed nothing before hanging, so it stuck somewhere before its final PASS line. Candidates: - a stream holding a connection or a cursor while a later step waits on a lock (the \`FOR UPDATE\` before \`stopHistory\`, or the cleanup's deletes); - \`store.idle()\` in the \`finally\` waiting on work that never finishes; - the refused \`revisionChunks\` and \`snapshotChunks\` generators keeping their connections after they reject. To do: reproduce it by looping the test against a local PostgreSQL, add progress logging, and find what's waiting (\`pg_stat_activity\` and \`pg_locks\` at the time of the hang). The job had no \`timeout-minutes\`, so GitHub would have let it run for six hours. A separate PR gives the core, browser and PostgreSQL jobs limits. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/issues/238
Related
- #237 Add full screen for the timeline
- #239 Give the core, browser and PostgreSQL CI jobs time limits
- #279 The document stream test can no longer hang on a failed check
- #288 The next-postgres test holds a preparing copy's mark while it checks it
- Give the core, browser and PostgreSQL jobs time limits
- The document stream test can no longer hang on a failed check
Open #238 document-stream-postgres can hang in CI in the timeline