Yuneng Jiang afb28540bb fix(e2e): keep the CLI determinism test out of the in-cluster suite ... It drives the real CLI for several seconds. The edge stamps every upstream call with PYTEST_CURRENT_TEST, a process-global that names whichever test the worker is in when the call arrives rather than the one that made it, so a test that holds a worker that long collects other tests' in-flight calls. Build 234's key report credits this test with 20 Bedrock and 7 Anthropic misses, and it makes no provider call at all. Those misattributed calls take the wrong test id into the cache key and write recordings under it, so the test was polluting the shared corpus it exists to protect. Deselected unless E2E_CLI_DETERMINISM is set, the same opt-in shape the managed-files, prompt-caching and redis-chaos markers already use. The attribution bug itself is older than this branch and is reported, not fixed here.		2026-09-16 16:01:32 -07:00
..
__init__.py	test(e2e): retry upstream-saturation failures in the claude CLI driver	2026-08-29 17:13:10 -07:00
test_request_determinism.py	fix(e2e): keep the CLI determinism test out of the in-cluster suite	2026-09-16 16:01:32 -07:00
test_retry_classification.py	test(e2e): retry upstream-saturation failures in the claude CLI driver	2026-08-29 17:13:10 -07:00