From a23fef3cee9e4c1dc4c1949bebf26c870eadd6f6 Mon Sep 17 00:00:00 2001 From: PJ Date: Tue, 2 Jun 2026 09:44:50 +0530 Subject: [PATCH] fix(chrome): raise DevTools websocket read timeout to 60s Chrome cold-start on a loaded CI runner can exceed chromedp's 20s default for reading the DevTools websocket URL, flaking the browser tests with "websocket url timeout reached". Give launch more headroom. --- internal/driver/chrome/driver.go | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/internal/driver/chrome/driver.go b/internal/driver/chrome/driver.go index 3a9aa51..4dc98eb 100644 --- a/internal/driver/chrome/driver.go +++ b/internal/driver/chrome/driver.go @@ -41,6 +41,10 @@ func New() *Driver { // CI runners give Chrome a tiny /dev/shm; without this the browser // process hangs on startup and never reports its DevTools socket. chromedp.Flag("disable-dev-shm-usage", true), + // Cold-starting Chrome on a loaded CI runner can take longer than the + // 20s default to print its DevTools websocket URL; give it more room + // so launch does not flake with "websocket url timeout reached". + chromedp.WSURLReadTimeout(60*time.Second), )..., ) tabCtx, tabCancel := chromedp.NewContext(allocCtx)