From c66f9f24971d9f6a753133006c61e5af6cfd2d38 Mon Sep 17 00:00:00 2001 From: Tim van der Meij Date: Thu, 14 May 2026 13:47:03 +0200 Subject: [PATCH] Reduce the protocol delay for Chrome in the integration tests Originally we introduced a small delay for Puppeteer operations in Chrome to avoid intermittent failures where protocol calls were happening too quickly in succession. However, since then a number of improvements were made, both locally and upstream, that reduce the need for this delay: - the integration tests have been hardened to remove (potential) sources of intermittent failures in many places; - the browsers and Puppeteer have been updated to improve performance and support for testing infrastructure; - the conversion to WebDriver BiDi has been completed, which replaced the Chrome-specific CDP protocol with a formalized protocol that could provide more safety guarantees. This commit therefore reduces the Chrome-specific delay from 5 to 3 milliseconds, which should nowadays be a better value to speed up the Chrome tests and bring them closer to Firefox in terms of runtime. --- test/test.mjs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/test.mjs b/test/test.mjs index fde169a81..d2adf6c3b 100644 --- a/test/test.mjs +++ b/test/test.mjs @@ -992,7 +992,7 @@ async function startBrowser({ // calls can run before events triggered by the previous protocol calls had // a chance to be processed (essentially causing events to get lost). This // value gives Chrome a more similar execution speed as Firefox. - options.slowMo = 5; + options.slowMo = 3; // avoid crash options.args = ["--no-sandbox", "--disable-setuid-sandbox"];