From 103e558b8e69c1ad33bb3f911e717fff2e33df41 Mon Sep 17 00:00:00 2001 From: Levi Zim Date: Sat, 20 Jun 2026 20:52:30 +0800 Subject: [PATCH] test: further limit the concurrency of WPTRunner for RISC-V Even when the concurrency of WPTRunner is limited to 10, flaky WPT tests are still observed on RISC-V with Sv39. For example, test/wpt/test-compression.js failed in https://github.com/riscv-forks/node-riscv/actions/runs/27756747452 and https://github.com/riscv-forks/node-riscv/actions/runs/27544719447, where the cause of the failure is a failing `mmap` of roughly 8GiB: [pid 954955] mmap(NULL, 8589996032, PROT_NONE, ... Further limit the concurrency of WPTRunner to fix flaky tests. See #60591 for the reason of limiting the WPT test concurrency on RISC-V. Signed-off-by: Levi Zim --- test/common/wpt.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/common/wpt.js b/test/common/wpt.js index 41c56e964f763e..b49573f2de2fc4 100644 --- a/test/common/wpt.js +++ b/test/common/wpt.js @@ -563,7 +563,7 @@ class WPTRunner { // memories(27 from a fresh node repl). Limit the concurrency to avoid // creating too many wasm memories that would fail. if (process.arch === 'riscv64' || process.arch === 'riscv32') { - concurrency = Math.min(10, concurrency); + concurrency = Math.min(5, concurrency); } this.path = path;