Michael Chihlas
0aefaa78eb
Capture the backend pytest parallelization work so it survives session end. Backend suite is currently ~22 min wall-clock for 1076 tests; xdist with one-DB-per-worker should land in the 3-6 min range on the homelab Gitea Actions runner. Also queues two backlog items: - Frontend lint warnings (23 react-hooks/exhaustive-deps after PR #149) - Periodic audit of the ResourceWarning filterwarnings added by Codex Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
TODO.md
Backlog of work NOT currently active. Read only when
CURRENT_TASK.mdstatus iscomplete. Format:- [ ] short description — optional link to issue/PR
Up next
- Parallelize backend pytest with pytest-xdist. Currently the backend suite takes ~22 min wall-clock for
1076 passed, 35 deselected(verified locally 2026-04-25). With-n autoon the homelab Gitea Actions runner, this should land in the 3–6 min range depending on core count. Blocker:test_dbfixture inbackend/tests/conftest.pydoesDROP SCHEMA public CASCADEper test, which two workers would race on. Standard fix: one database per worker, derived fromPYTEST_XDIST_WORKERenv var inside conftest. The runner has spare CPU, so prioritize once main is green and the 54-failure cleanup has landed.
Backlog
- Frontend lint warnings cleanup. 23
react-hooks/exhaustive-depswarnings remain after PR #149 (mostly missing-deps in useEffect). Either fix them or audit them for known-safe ones and add eslint-disable comments. Not blocking CI today. - Audit
filterwarningsignores added inwip(handoff): restore backend suite to green. Codex added narrowResourceWarningfilters for unclosed socket/transport/event-loop noise from pytest-asyncio teardown. Worth periodically reviewing whether those are still needed (e.g. when bumping pytest-asyncio) — if a real warning appears in those forms it would be silenced.