perf(ci): pytest-xdist with per-worker DBs — 22m → ~4m backend suite #151

chihlasm · 2026-04-25T16:08:30Z

chihlasm commented

2026-04-25 16:08:30 +00:00

Superseded by PR #150 — its branch now contains both the xdist parallelization (originally this PR's scope) and the e2e selector fixes. One consolidated CI-recovery PR is easier to land than three stacked ones.

chihlasm added 6 commits 2026-04-25 16:08:30 +00:00

fix(ci): set DATABASE_TEST_URL + downgrade upload-artifact to v3 (Gitea Actions)

Mirror to GitHub / mirror (push) Successful in 11s

Details

CI / backend (pull_request) Failing after 28m29s

Details

CI / frontend (pull_request) Successful in 3m11s

Details

CI / e2e (pull_request) Failing after 4m56s

Details

8f7df2c0ef

Two CI-config issues blocking the gate from going green:

1. **Backend tests connect to localhost instead of postgres service.**
   conftest.py reads DATABASE_TEST_URL only — DATABASE_URL is intentionally
   not consulted (per dab740d's test-DB-isolation hardening — running
   pytest with DATABASE_URL set previously dropped the dev DB schema).
   The CI workflow only sets DATABASE_URL, so conftest falls back to its
   localhost default and every fixture-setup fails with
   `OSError: Connect call failed ('127.0.0.1', 5432)` — observed as 638
   errors on the latest main run.

   Add DATABASE_TEST_URL pointing at the postgres service container.
   Same connection string as DATABASE_URL — the test DB and the app DB
   are the same physical postgres in CI; conftest's safety assertion is
   satisfied by the URL containing "test".

2. **Frontend artifact upload fails on Gitea Actions runner.**
   actions/upload-artifact@v4 (and v5) are not supported on Gitea
   Actions / GHES — the runner returns
   `GHESNotSupportedError: ... not currently supported on GHES`. Lint
   itself is now passing (0 errors after PR #149); the job exits 1 only
   because the upload step then fails.

   Pin upload-artifact + download-artifact to v3, the latest version
   compatible with Gitea Actions until they ship v4 support.

After this lands, both backend and frontend CI gates should turn
green — at which point we can also add backend to the required status
checks on main.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

docs(ai): handoff for Codex — CI recovery + 54 real backend failures

Mirror to GitHub / mirror (push) Successful in 11s

Details

CI / backend (pull_request) Failing after 28m15s

Details

CI / frontend (pull_request) Successful in 2m55s

Details

CI / e2e (pull_request) Failing after 4m23s

Details

208ec996d5

Updates HANDOFF.md, CURRENT_TASK.md, and SESSION_LOG.md so the next
session has accurate resume state. Summary of where things are:

- PR #141 (PSA tickets), PR #147 (FlowPilot Phase 1-9), PR #148 (CI
  fixes part 1), PR #149 (CI fixes part 2) all merged to main in this
  session.
- Branch protection enabled on main: PR-only, CI / frontend required.
- PR #150 (this branch) is the last CI-config PR — adds
  DATABASE_TEST_URL to the workflow and pins upload-artifact to v3.
- Next session: watch #150's CI, merge if green, add CI / backend to
  required checks, then start on the 54 real backend test failures.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

wip(handoff): restore backend suite to green

Mirror to GitHub / mirror (push) Successful in 12s

Details

CI / backend (pull_request) Failing after 27m35s

Details

CI / frontend (pull_request) Successful in 2m46s

Details

CI / e2e (pull_request) Failing after 4m9s

Details

49f88569da

Co-Authored-By: Codex <noreply@openai.com>

docs(ai): queue pytest-xdist parallelization in TODO.md

Mirror to GitHub / mirror (push) Successful in 11s

Details

CI / frontend (pull_request) Has been cancelled

Details

CI / e2e (pull_request) Has been cancelled

Details

CI / backend (pull_request) Has been cancelled

Details

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>

fix(ci): mock AI provider in record_decision test + cache pip/npm + drop term-missing

Mirror to GitHub / mirror (push) Successful in 12s

Details

CI / backend (pull_request) Successful in 31m8s

Details

CI / frontend (pull_request) Successful in 5m42s

Details

CI / e2e (pull_request) Failing after 4m57s

Details

e976fb4e87

Three changes that get PR #150 to a green CI gate:

1. **test_record_decision_persists_and_bumps_state_version** — the
   `decision: draft_template` path calls `_extract_template_parameters`
   (TemplateExtractionService → AI provider). CI doesn't set
   ANTHROPIC_API_KEY/GOOGLE_AI_API_KEY, so the endpoint raised
   `RuntimeError: No AI provider configured` and returned 500. The test
   isn't exercising the AI integration — patched the extractor with an
   AsyncMock returning a minimal valid `{templated_body, parameters}`
   dict. Verified locally: the test now passes.

2. **pip + npm caches** in backend, frontend, and e2e jobs. Keyed on
   the hash of requirements*.txt / package-lock.json with a runner-os
   restore-key fallback. Saves ~30-60s per run on cache hit.

3. **Pytest invocation tightened**:
   - Dropped `--cov-report=term-missing` — the custom "Display coverage
     summary" step below parses coverage.json and prints the same
     module list more concisely. Term-missing dumps every uncovered
     line which adds ~5-10s of stdout.
   - Added `--maxfail=10` so a structural breakage (fixture explosion,
     DB unreachable) bails after 10 errors instead of running the full
     25-min suite. Tunable.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

perf(ci): pytest-xdist with per-worker DBs — 22m → ~4m

Mirror to GitHub / mirror (push) Successful in 12s

Details

CI / backend (pull_request) Successful in 9m37s

Details

CI / frontend (pull_request) Successful in 5m42s

Details

CI / e2e (pull_request) Failing after 20m54s

Details

ca45bc9bb3

Backend suite is the slow gate (1076 passed locally in 22m27s on
fix/ci-workflow-config). Adding pytest-xdist with per-worker DB
isolation drops it to ~4m20s on the 8-core homelab runner. Verified
locally: `pytest -n auto --no-cov` finished in 4m28s real time
(15m19s user — confirms ~5× parallelism).

How it works:
- conftest.py reads `PYTEST_XDIST_WORKER` (set per worker by xdist —
  'gw0', 'gw1', …). When set, derives a per-worker DB URL like
  `…/resolutionflow_test_gw0`. The base DB stays for serial / master
  runs.
- `_ensure_worker_db_exists` runs synchronously at conftest import,
  connects to the postgres maintenance DB, and `CREATE DATABASE`s the
  worker-suffixed DB if it doesn't exist. Idempotent across runs.
- The "test" safety guard still applies — every worker DB name
  contains "test" so the assertion holds.
- The per-test `DROP SCHEMA public CASCADE` now operates on the
  worker's isolated DB, no cross-worker race.

CI workflow: backend job switches to `pytest -n auto`. Coverage still
collected (pytest-cov has built-in xdist support).

Adds `pytest-xdist==3.6.1` to requirements-dev.txt.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

chihlasm referenced this issue from a commit

2026-04-25 16:15:09 +00:00

docs(ai): handoff after CI parallelization + final test fix

chihlasm referenced this issue from a commit

2026-04-25 19:26:23 +00:00

docs(ai): queue data-testid hardening + reflect PR #152 + 3-runner setup

chihlasm closed this pull request

2026-04-25 19:54:08 +00:00

Mirror to GitHub / mirror (push) Successful in 12s

Details

CI / backend (pull_request) Successful in 9m37s

Required