Skip to content

updpatch: nodejs 25.8.1-1#5172

Merged
felixonmars merged 2 commits into
felixonmars:masterfrom
kxxt:nodejs
Mar 21, 2026
Merged

updpatch: nodejs 25.8.1-1#5172
felixonmars merged 2 commits into
felixonmars:masterfrom
kxxt:nodejs

Conversation

@kxxt
Copy link
Copy Markdown
Contributor

@kxxt kxxt commented Mar 21, 2026

  • Refresh patch

  • This PR depends on updpatch: simdjson 1:4.4.1-1 #5171

  • nocheck is needed because:

    [16:33:50.263] ERROR: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instance
    RangeError: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instancemake[1]: *** [Makefile:392: test/addons/.docbuildstamp] Error 1
    make: *** [Makefile:352: test-only] Error 2
    

- Refresh patch
- This PR depends on felixonmars#5171
- nocheck is needed because:

	[16:33:50.263] ERROR: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instance
	RangeError: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instancemake[1]: *** [Makefile:392: test/addons/.docbuildstamp] Error 1
	make: *** [Makefile:352: test-only] Error 2
@felixonmars
Copy link
Copy Markdown
Owner

  • [16:33:50.263] ERROR: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instance

We could also blacklist it for sv39 builders for now, until wasm issues get solved (if that's still the issue).

@kxxt
Copy link
Copy Markdown
Contributor Author

kxxt commented Mar 21, 2026

  • [16:33:50.263] ERROR: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instance

We could also blacklist it for sv39 builders for now, until wasm issues get solved (if that's still the issue).

I will fix it in upstream like nodejs/node#60591.

@kxxt
Copy link
Copy Markdown
Contributor Author

kxxt commented Mar 21, 2026

I have added it to sv39 blacklist. Hopefully it will only stay there temporarily.

@felixonmars felixonmars merged commit b397aba into felixonmars:master Mar 21, 2026
1 check passed
@kxxt
Copy link
Copy Markdown
Contributor Author

kxxt commented Mar 21, 2026

  • [16:33:50.263] ERROR: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instance

We could also blacklist it for sv39 builders for now, until wasm issues get solved (if that's still the issue).

I will fix it in upstream like nodejs/node#60591.

The fix is nodejs/doc-kit#691.

@kxxt kxxt deleted the nodejs branch March 21, 2026 07:30
kxxt added a commit to kxxt/archriscv-packages that referenced this pull request Mar 23, 2026
- This depends on felixonmars#5172
- Refresh patch and drop upstreamed patches.
- Add v8 patch to fix build: https://chromium-review.googlesource.com/c/v8/v8/+/7608971
- Arch almost always use `_manual_clone` now so let's follow suit.
  - Add a retry for `gclient sync` because it often fail on SG2042 with
    `lockfile.LockError: Error locking /build/chromium/src/chromium-checkout/depot_tools/external_bin/gsutil/gsutil_5.35 (err: [Errno 11] Resource temporarily unavailable)`
  - Install dependencies from pypi to `rv-site-packages` and add it to
    `PYTHONPATH` because chromium does not distribute bundled wheels for
    riscv.
  - Patch `DEPS` to drop binary dependencies because they are not available
    for riscv.
felixonmars pushed a commit that referenced this pull request Apr 5, 2026
- This depends on #5172
- Refresh patch and drop upstreamed patches.
- Add v8 patch to fix build: https://chromium-review.googlesource.com/c/v8/v8/+/7608971
- Arch almost always use `_manual_clone` now so let's follow suit.
  - Add a retry for `gclient sync` because it often fail on SG2042 with
    `lockfile.LockError: Error locking /build/chromium/src/chromium-checkout/depot_tools/external_bin/gsutil/gsutil_5.35 (err: [Errno 11] Resource temporarily unavailable)`
  - Install dependencies from pypi to `rv-site-packages` and add it to
    `PYTHONPATH` because chromium does not distribute bundled wheels for
    riscv.
  - Patch `DEPS` to drop binary dependencies because they are not available
    for riscv.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants