mirror of
https://github.com/BerriAI/litellm.git
synced 2026-09-09 22:31:41 +00:00
BadRequestErrorRetries and ContentPolicyViolationErrorRetries did let a retry happen, but the retry re-picked the deployment that had just refused, since a 400 never puts a deployment in cooldown. On a weighted model group the caller got the same 400 back after every configured retry, and the existing 401/403 "retry on another deployment" rule broke the same way A retry after a non-transient status now carries the deployments that already answered this request in the per-request exclusion list weighted failover already honors, so the next attempt lands on a sibling. Single-deployment groups still retry in place, and 408/429/5xx retries are untouched Adds live e2e coverage for reliability.retry.context_window.succeeds_within_retries and renames the two litellm.utils deployment filters that are now called from outside the module |
||
|---|---|---|
| .. | ||
| 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_fallbacks_e2e.py | ||
| test_reliability_retries_e2e.py | ||
| test_reliability_timeouts_e2e.py | ||