mirror of
https://github.com/BerriAI/litellm.git
synced 2026-10-02 02:11:58 +00:00
4b1d9bf148
The timeout reliability tests rely on a 1ms deadline the real backend always misses. With E2E_PROVIDER_CACHE on, the deployment pointed at the cache edge, and its healthy sibling in the same test had already recorded a response for the same canonical request, so the edge answered from Redis inside the 1ms read window. Build 342 of litellm-e2e saw test_timeout_trips_cooldown_then_recovers get a 200 from the timing-out deployment itself, with a recording made about 12 hours earlier. Both timeout helpers now register on the live provider path, which PROVIDER_CACHE.md reserves for tests that need real provider timing |
||
|---|---|---|
| .. | ||
| complexity_router_client.py | ||
| conftest.py | ||
| reliability_support.py | ||
| test_auto_router_regressions_e2e.py | ||
| test_complexity_router_e2e.py | ||
| test_reliability_cache_e2e.py | ||
| test_reliability_cancel_on_disconnect_e2e.py | ||
| test_reliability_cooldowns_e2e.py | ||
| test_reliability_fallbacks_e2e.py | ||
| test_reliability_memory_e2e.py | ||
| test_reliability_prompt_caching_e2e.py | ||
| test_reliability_retries_e2e.py | ||
| test_reliability_routing_strategies_e2e.py | ||
| test_reliability_timeouts_e2e.py | ||