5 Commits

Include renames

Author	SHA1	Message	Date
bermudalambandClaude Opus 5	8d082d100f	ci: run backend integration tests as a separate manual workflow ... The job was holding the runner for hours on every push and pull request. On 2026-08-18 it ran 3h12m, and because the runner is sequential it kept frontend-e2e queued behind it for that whole time. It is not a slow suite. That run executed 89 tests in 87 seconds, then logged "Jest did not exit one second after the test run has completed" and sat there until something killed it — an open handle keeping the event loop alive after the run finishes. The same run also failed with relation "orders" does not exist, so the schema was missing in CI even though globalSetup migrates. Neither is root-caused yet; both follow the job into its new home. So the new workflow carries a 15-minute timeout. The suite needs about 90 seconds, so this is not a performance budget — it is a stop that turns a post-run hang into minutes of wasted runner time rather than hours. Tests.yml keeps a comment saying where the job went, so its absence reads as deliberate rather than as something lost in an edit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-18 09:00:47 -05:00
bermudalambandClaude Opus 5	ec63b9cdb0	fix: unset NODE_ENV in e2e job so devDependencies install ... npm treats NODE_ENV=production as --omit=dev, so `npm install` in the frontend-e2e job skipped typescript and the build died on `tsc: not found`. The same env var would have stripped vite and @playwright/test from the frontend install, and flipped the session cookie to Secure on a run served over plain http. The reported summarize crash was a symptom: the job aborted before Playwright ran, but Summarize is `if: always()` and threw ENOENT on the missing JSON, burying the real failure. Both summarize scripts now report the missing file and exit 0 -- the job still fails via its own step. Also split build from start, replaced `sleep 3` with a readiness poll against /api/config, and dump the backend log when e2e fails. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-15 08:56:25 -05:00
bermudalamb	483b1391a5	fix: use node-pg-migrate instead of deleted init.sql in e2e workflow	2026-08-14 16:18:20 -05:00
bermudalamb	2bff3a231f	ci: fix Postgres service port conflict in CI	2026-08-14 08:41:40 -05:00
bermudalamb	234330e482	Add CI test workflow with job summaries	2026-08-13 19:10:30 -05:00