Kerry Lu 058ff8c63c test(e2e): keep answering while every Redis command times out ... Add tests/e2e/router/test_redis_timeout_e2e.py against a proxy booted from tests/e2e/gateway/redis_timeout_ci_config.yml: a real Redis with socket_timeout 0.001, so every command times out and the circuit breaker opens, plus a primary deployment that always fails and falls back to a healthy one, so every request carries retry breadcrumbs into cost tracking. The test drives twenty chat requests through the proxy and asserts each answers within ten seconds, the last third is no slower than the first, /health/liveliness stays fast, and every request still reaches the spend log. Gate it behind the redis_timeout marker and E2E_REDIS_TIMEOUT, exclude it from the per-PR e2e-changed selector, register the reliability.circuit_breaker.redis_timeout.stays_responsive cell, and run it as its own job in the weekly load anomaly workflow with a Postgres and Valkey service. Against a v1.100.0 proxy the run wedges the worker: requests time out and liveliness stops answering (LIT-6780). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014ZDULyJPp17ZFiJenRxs2T		2026-09-09 15:43:50 -07:00
..
assert_tests_ran.py	ci(e2e): run the access_control canary on harness changes and name failed tests	2026-09-05 18:46:51 -07:00
down.sh	ci(e2e): run a PR's changed e2e tests three times behind a human-approved environment	2026-09-02 14:53:40 -07:00
secrets_to_env.py	fix(e2e-changed): keep the gate off suites the stack cannot run	2026-09-05 21:03:50 -07:00
select_tests.py	test(e2e): keep answering while every Redis command times out	2026-09-09 15:43:50 -07:00
up.sh	fix(e2e): wait for every gateway before using a new model and keep the network rerun	2026-09-05 16:10:40 -07:00