test(proxy-ccr): align retrieve/stats assertions with 1800s CCR TTL default

The CCR store default TTL moved 300 -> 1800 (session-scale); two
assertions in test_proxy_ccr.py still expected the old 300s value in
the miss-detail string and the stats endpoint. test_compression_store
and test_ccr were already updated; this was the last straggler.
This commit is contained in:
Tejas Chopra 2026-06-13 22:03:38 -07:00
parent b44a70d669
commit 7cb0f43b73

View file

@ -67,7 +67,7 @@ class TestCCRRetrieveEndpoint:
response = client.post("/v1/retrieve", json={"hash": "nonexistent123"})
assert response.status_code == 404
assert "Entry not found" in response.json()["detail"]
assert "CCR TTL: 300 seconds" in response.json()["detail"]
assert "CCR TTL: 1800 seconds" in response.json()["detail"]
def test_retrieve_expired_hash_reports_expiration_detail(self, client):
"""Expired entries report expiration separately from missing hashes."""
@ -263,7 +263,7 @@ class TestCCRStatsEndpoint:
data = response.json()
assert "store" in data
assert data["store"]["entry_count"] == 0
assert data["store"]["default_ttl_seconds"] == 300
assert data["store"]["default_ttl_seconds"] == 1800
assert "recent_retrievals" in data
def test_stats_exposes_env_configured_ttl(self, client, monkeypatch):