Skip to content

Postgres+pgvector CI job running the ignored integration suites #106

Closed

Description

@tonibergholm

Question

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.

Activity

  1. added
    ready-for-agentScoped and unambiguous enough for an agent to pick up
    wayfinder:taskWayfinder ticket: work that unblocks a decision or lands a fix
    on Jul 9, 2026
  2. self-assigned this
    on Jul 9, 2026
  3. tonibergholm commented on Jul 9, 2026

    @tonibergholm
    MemberAuthor

    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 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.

  4. added a commit that references this issue on Jul 9, 2026
    195d83d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

ready-for-agentScoped and unambiguous enough for an agent to pick upwayfinder:taskWayfinder ticket: work that unblocks a decision or lands a fix

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions