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
{{ message }}
Repository navigation
Postgres+pgvector CI job running the ignored integration suites #106
Fix audit finding #6 (medium): the standard Rust CI job never runs the ignored Postgres-dependent tests — only the fake-GCS ignored suite is explicitly run (evidence: .github/workflows/ci.yml:33, .github/workflows/ci.yml:55). Repo policy already requires real Postgres+pgvector for snapshot/restore tests; this enforces it.
Scope:
Add a Postgres+pgvector service/job to CI that runs the ignored memory, reverse-migration, and commit-with-memory suites (--ignored).
This ticket lands EARLY by design — it is the verification harness for the get_raw-integrity and ADR-0014 fixes that follow.
Resolution records: PR link, which suites now run in CI, job runtime.
What landed: a postgres CI job with a pgvector/pgvector:pg16 service container mirroring the demo's image/credentials, a CREATE EXTENSION IF NOT EXISTS vector step (the adapter checks but can't create it), and all three ignored Postgres suites: agentic-memory integration (17 tests), reverse_migration (3), commit_with_memory (1) — 21 tests total, verified green locally with the exact CI commands before pushing.
A real catch: the memory suite reproducibly fails 2 tests in default parallel mode against real Postgres (ac1_writes_during_restore_are_reverted — schema-name 23505 collision; snapshot_strict_drain_preserves_bad_row_on_block — snapshot didn't block). This is the suite's own documented contract, not a product bug: public.agentic_change_log is shared across test schemas by design, so the module doc mandates --test-threads=1. The job honors that; logged as bug-128 in .wolf/buglog.json.
Facts later tickets depend on: the harness the get_raw-integrity fix (#110, now unblocked once this closes) and the ADR-0014 gate (#111) rely on is live — their Postgres-path regression tests will run on every PR. Job runtime ~2 minutes; DATABASE_URL in CI is postgres://agentic:agentic@localhost:54322/agentic.
Activity
tonibergholm commentedon Jul 9, 2026
Resolution
Shipped as PR #116 (pending Toni's review/merge per the map's PR gate). The new job ran green on the PR's own CI: postgres integration (pgvector), 2m0s.
What landed: a
postgresCI job with apgvector/pgvector:pg16service container mirroring the demo's image/credentials, aCREATE EXTENSION IF NOT EXISTS vectorstep (the adapter checks but can't create it), and all three ignored Postgres suites:agentic-memoryintegration (17 tests),reverse_migration(3),commit_with_memory(1) — 21 tests total, verified green locally with the exact CI commands before pushing.A real catch: the memory suite reproducibly fails 2 tests in default parallel mode against real Postgres (
ac1_writes_during_restore_are_reverted— schema-name 23505 collision;snapshot_strict_drain_preserves_bad_row_on_block— snapshot didn't block). This is the suite's own documented contract, not a product bug:public.agentic_change_logis shared across test schemas by design, so the module doc mandates--test-threads=1. The job honors that; logged as bug-128 in.wolf/buglog.json.Facts later tickets depend on: the harness the get_raw-integrity fix (#110, now unblocked once this closes) and the ADR-0014 gate (#111) rely on is live — their Postgres-path regression tests will run on every PR. Job runtime ~2 minutes; DATABASE_URL in CI is
postgres://agentic:agentic@localhost:54322/agentic.Run the ignored Postgres integration suites in CI against real pgvect…