Flaky/order-dependent test: test_cloud_provider_prompt_filters_disallowed_metadata #174

New issue

Closed

opened 2026-08-01 05:58:34 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-08-01 05:58:34 +00:00

Contributor

Observed during #142 verification on the dev server: tests/test_ai_summarizer.py::test_cloud_provider_prompt_filters_disallowed_metadata failed in one full-suite run on feat/event-export, then passed: in isolation, when run directly after the new export tests, and in an immediate full-suite rerun of the identical tree. The branch touches no AI code, so this is a pre-existing order-dependent or flaky failure — likely shared mutable state (settings cache, provider registry, or similar) leaking from some earlier test under one particular ordering.

Suggest folding into #141's test-infrastructure pass: reproduce with pytest -p no:randomly orderings or --last-failed bisection, find the polluting test, and fix the shared-state leak rather than the symptom.

Observed during #142 verification on the dev server: `tests/test_ai_summarizer.py::test_cloud_provider_prompt_filters_disallowed_metadata` failed in one full-suite run on `feat/event-export`, then passed: in isolation, when run directly after the new export tests, and in an immediate full-suite rerun of the identical tree. The branch touches no AI code, so this is a pre-existing order-dependent or flaky failure — likely shared mutable state (settings cache, provider registry, or similar) leaking from some earlier test under one particular ordering. Suggest folding into #141's test-infrastructure pass: reproduce with `pytest -p no:randomly` orderings or `--last-failed` bisection, find the polluting test, and fix the shared-state leak rather than the symptom.

claude-bot referenced this issue

2026-08-01 05:58:47 +00:00

Explorer: event JSON export (#142) #175

claude-bot referenced this issue

2026-08-01 06:03:07 +00:00

History query performance, indexing, and Postgres-tier tests #141