From 69cac95f6fe4ff6e4cb30519c56bad7120b6d100 Mon Sep 17 00:00:00 2001 From: Raine Virta Date: Mon, 14 Sep 2026 19:21:16 +0300 Subject: [PATCH] stabilize cold streaming smoke test The streaming smoke test used a 500 ms deadlock guard around construction of all provider clients, application setup, lazy tokenizer initialization, and the HTTP streaming handshake. Measured cold initialization takes roughly 1.4 to 1.6 seconds on macOS: native-root client construction accounts for about 0.9 seconds and first-use tokenizer setup takes about 0.5 seconds. Use a three-second outer guard so the test accommodates measured cold setup with CI scheduling margin. The upstream terminal event remains blocked by the fixture's notification gate, so returning headers still proves streaming starts before upstream completion. Keep the separate 200 ms first-frame assertion unchanged. --- tests/smoke_cutover.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/smoke_cutover.rs b/tests/smoke_cutover.rs index d32aae1c..b8ff34a2 100644 --- a/tests/smoke_cutover.rs +++ b/tests/smoke_cutover.rs @@ -1734,7 +1734,7 @@ async fn smoke_codex_http_stream_returns_before_upstream_completion() { let _base_url_env = EnvGuard::set("CCP_CODEX_BASE_URL", &upstream); let _transport_env = EnvGuard::set("CCP_CODEX_TRANSPORT", "http"); let response = tokio::time::timeout( - Duration::from_millis(500), + Duration::from_secs(3), call_messages_body(json!({ "model": "gpt-5.5", "max_tokens": 64,