From 98e30c896caf129c11299c427863ff8defc4d54b Mon Sep 17 00:00:00 2001 From: moreih29 Date: Fri, 20 Nov 2026 02:04:44 +0900 Subject: [PATCH] test(chat): give the Windows cmd-to-Node stdin test 30 s The whole run takes under a second, but on a fresh windows-latest runner the first cmd and Node start once passed the 10 s deadline (chat.send: context deadline exceeded), failing the release PR's agent tests. A rerun passed. Only this test's deadline changes; what it checks stays the same. Co-Authored-By: Claude Opus 5.5 --- internal/chat/stdin_windows_test.go | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/internal/chat/stdin_windows_test.go b/internal/chat/stdin_windows_test.go index 08d531701..6bdbc9f48 100644 --- a/internal/chat/stdin_windows_test.go +++ b/internal/chat/stdin_windows_test.go @@ -49,7 +49,9 @@ process.stdin.on("end", () => process.stdout.write('{"eof":true}\n')); } return rec.sink(event, payload) }) - ctx, cancel := context.WithTimeout(context.Background(), 10*time.Second) + // A whole run takes well under a second, but the first cmd and Node start + // on a fresh Windows runner has taken over 10 s, so allow 30 s here alone. + ctx, cancel := context.WithTimeout(context.Background(), 30*time.Second) defer cancel() key := tabKey{workspaceID: "ws", tabID: "windows-node-stdin"}