Skip to content

test: gate sqlite-backed inference_fixture tests on store-sqlite - #1292

Merged
leseb merged 1 commit into
praxis-proxy:mainfrom
leseb:leseb/fix-issue-1280
Sep 22, 2026
Merged

leseb merged 1 commit into
praxis-proxy:mainfrom
leseb:leseb/fix-issue-1280

Conversation

@leseb

@leseb leseb commented Sep 22, 2026

Copy link
Copy Markdown
Collaborator

Summary

The four inference_fixture tests that stand up the Responses proxy with a sqlite-backed response store panic at pipeline-build time (openai_response_store: backend 'sqlite' is unavailable; rebuild with the 'store-sqlite' feature) whenever compiled without store-sqlite, which is exactly what make test (cargo test --workspace, default features = store-postgres only) does — so they were red locally and in release.yaml while integration.yaml kept them green under store-all. This gates those four tests plus their two exclusively-used helpers on #[cfg(feature = "store-sqlite")] (matching the precedent in apis/src/store/mod.rs), so default-feature runs compile them out and store-all runs still exercise them. No production or CI changes — the smallest complete fix.

Related issue

Closes #1280

Validation

  • cargo test -p praxis-test-utils inference_fixture (default features) → 313 passed / 0 failed / 0 ignored

  • cargo test -p praxis-test-utils --no-default-features --features store-all inference_fixture → 317 passed / 0 failed (the 4 gated tests active)

  • cargo clippy -p praxis-test-utils --all-targets and … --no-default-features --features store-all → clean, exit 0

  • cargo +nightly fmt --all -- --check → clean

  • Unit tests

  • Integration or functional tests (test-only change; the affected tests already run under store-all in integration.yaml)

  • make lint (ran the relevant subset — clippy + nightly fmt on the changed crate under both feature sets — clean)

Checklist

  • I reviewed every changed line and can explain the change.
  • New capabilities include an example config and functional example test. (N/A — test-only)
  • User-facing behavior and generated documentation are updated. (N/A — test-only)
  • Performance-sensitive changes include appropriate benchmark or load-test evidence. (N/A)
  • Commits are signed and include a Signed-off-by trailer.

Breaking changes

None.

The record_live and materialize/replay-config inference_fixture tests stand up the Responses proxy with a sqlite-backed response store, so they panic at pipeline-build time ("openai_response_store: backend 'sqlite' is unavailable; rebuild with the 'store-sqlite' feature") whenever compiled without the store-sqlite feature. `make test` runs `cargo test --workspace` under the default features (store-postgres only), so these tests were red locally and in release.yaml while integration.yaml (which runs them under store-all) stayed green.

Gate the four sqlite-dependent tests and their two exclusively-used helpers on #[cfg(feature = "store-sqlite")], matching the precedent in apis/src/store/mod.rs. Default features compile them out (313 pass); store-all still exercises them (317 pass).

Signed-off-by: Sébastien Han <seb@redhat.com>
@leseb
leseb requested review from a team and pierDipi September 22, 2026 09:39
@leseb
leseb merged commit d166d0d into praxis-proxy:main Sep 22, 2026
30 checks passed
@leseb
leseb deleted the leseb/fix-issue-1280 branch September 22, 2026 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

praxis-test-utils inference_fixture tests are red on main and PR CI does not run them

1 participant