Repository navigation
Conversation
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 nodejs#60591 for the reason of limiting the WPT test concurrency on RISC-V. Signed-off-by: Levi Zim <rsworktech@outlook.com>
kxxt
force-pushed
the
wpt-lower-concurrency-riscv
branch
from
June 20, 2026 13:02
9ca18b2 to
103e558
Compare
6 of 10 tasks
sxa
approved these changes
Sep 4, 2026
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
mmapof roughly 8GiB:Further limit the concurrency of WPTRunner to fix flaky tests. See #60591 for the reason of limiting the WPT test concurrency on RISC-V.
CC @nodejs/platform-riscv64