Skip to content

test: limit the concurrency of WPTRunner for RISC-V #60591

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 11, 2025
+8 −0
Merged

test: limit the concurrency of WPTRunner for RISC-V #60591

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions test/common/wpt.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -533,6 +533,14 @@ const limit = (concurrency) => {

class WPTRunner {
constructor(path, { concurrency = os.availableParallelism() - 1 || 1 } = {}) {
// RISC-V has very limited virtual address space in the currently common
// sv39 mode, in which we can only create a very limited number of wasm
// 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);
}

this.path = path;
this.resource = new ResourceLoader(path);
this.concurrency = concurrency;
Expand Down
Loading