deps: update V8 to 15.2 - #65161

Open
targos wants to merge 31 commits into
nodejs:mainfrom
targos:v8-152
Open

deps: update V8 to 15.2#65161
targos wants to merge 31 commits into
nodejs:mainfrom
targos:v8-152

Conversation

@targos

@targostargos commented Aug 9, 2026

Copy link
Copy Markdown
Member

Refs: #64784

@nodejs-github-bot

nodejs-github-bot commented Aug 9, 2026•
edited by targos
Loading

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/gyp
  • @nodejs/security-wg
  • @nodejs/v8

@targostargos changed the title deps: update V8 to 15.2.124.7deps: update V8 to 15.2Aug 9, 2026
@nodejs-github-botnodejs-github-bot added build Issues and PRs related to Node.js builds or CI infrastructure. dependencies PRs that add, update, or configure Node.js dependencies. needs-ci PRs that need a full CI run. labels Aug 9, 2026
@targostargos mentioned this pull request Aug 9, 2026
Open
@targos

targos commented Aug 9, 2026

Copy link
Copy Markdown
MemberAuthor

I guess this is blocked by #64408 (https://github.com/nodejs/node/actions/runs/31307061482/job/93228984418?pr=65161)

@joyeecheung

joyeecheung commented Aug 10, 2026

Copy link
Copy Markdown
Member

Uploaded https://chromium-review.googlesource.com/c/v8/v8/+/8223266 to fix the Linux AArch64 build (haven't tested on real Linux AArch64 yet, but that's what the error message suggests)

hubot pushed a commit to v8/v8 that referenced this pull request Aug 13, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[simd] Disable SVE implementation of array search for GCC
68cf9ec
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs/node#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
targos pushed a commit to targos/node that referenced this pull request Aug 13, 2026
@joyeecheung@targos
deps: V8: cherry-pick 68cf9ecd884b
d356533
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@richardlau

richardlau commented Aug 13, 2026

Copy link
Copy Markdown
Member

FWIW https://chromium-review.googlesource.com/c/v8/v8/+/8236132 was opened by @sravani1510 to address the AIX build failure that is occurring on our V8 nightly builds.

@targos

targos commented Aug 13, 2026

Copy link
Copy Markdown
MemberAuthor

@nodejs/platform-windows We're hitting a weird error on Windows:

https://github.com/nodejs/node/actions/runs/31699320590/job/94444346312?pr=65161

 Unexpected command-line argument "src/debug/debug-wasm-obects.q", expected a .tq file.
C:\Program Files\Microsoft Visual Studio\18\Enterprise\MSBuild\Microsoft\VC\v180\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for '..\..\out\Release\\torque.exe' exited with code 3. [D:\a\node\node\tools\v8_gypfiles\run_torque.vcxproj]

This wrong path doesn't exist in the code.

@targos

targos commented Aug 13, 2026

Copy link
Copy Markdown
MemberAuthor

@legendecas Can you help with the perfetto build?

@legendecas

legendecas commented Aug 14, 2026

Copy link
Copy Markdown
Member

Fixed the perfetto build. But I think the CI is failing for tests in large pages. Likely not related.

@targos

targos commented Aug 14, 2026

Copy link
Copy Markdown
MemberAuthor

Thanks. Summary of the remaining issues in GitHub CI:

I'll start a Jenkins CI for more coverage.

@nodejs-github-bot

nodejs-github-bot commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

CI: https://ci.nodejs.org/job/node-test-pull-request/75841/

@nodejs-github-bot

nodejs-github-bot commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark-ubuntu2404-intel-64,v8test=v8test/7311/

@nodejs-github-bot

nodejs-github-bot commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/

@nodejs-github-bot

nodejs-github-bot commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/

@richardlau

richardlau commented Aug 14, 2026

Copy link
Copy Markdown
Member

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/

Been talking to @miladfarca about this:

16:01:57 === mjsunit/maglev/regress-498816446-3 ===
16:01:57 --- stderr ---
16:01:57 V8 is running with experimental features enabled. Stability and security will suffer.
16:01:57 --- stdout ---
16:01:57 test/mjsunit/maglev/regress-498816446-3.js:25: RangeError: Array buffer allocation failed
16:01:57 ta = new Int32Array(0xffffffff+1);
16:01:57 ^
16:01:57 RangeError: Array buffer allocation failed
16:01:57 at new ArrayBuffer (<anonymous>)
16:01:57 at new Int32Array (<anonymous>)
16:01:57 at test/mjsunit/maglev/regress-498816446-3.js:25:6
16:01:57 Command: out.gn/s390x.release/d8 --test test/mjsunit/mjsunit.js test/mjsunit/maglev/regress-498816446-3.js --random-seed=-770474680 --nohard-abort --allow-natives-syntax --maglev-object-tracking --maglev
16:01:57 16:01:57 ===
16:01:57 === 1 tests failed
16:01:57 ===
16:01:57 >>> 17287 base tests produced 15072 (87%) non-filtered tests
16:01:57 >>> 15072 tests ran

The Linux ppc64le and s390x machines being tested on have 8GB RAM and this test is allocating 16GB.

@miladfarca

miladfarca commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Patched it here: https://crrev.com/c/8252113

This was referenced Aug 18, 2026
Open
Merged
@joyeecheung

joyeecheung commented Aug 19, 2026

Copy link
Copy Markdown
Member

For the SEA test failures: they should not have run in the first place. #63751 should fix it.

@joyeecheung

joyeecheung commented Aug 20, 2026

Copy link
Copy Markdown
Member

This should fix the alpine failures https://chromium-review.googlesource.com/c/v8/v8/+/8254825

@sxasxa mentioned this pull request Aug 20, 2026
Open
hubot pushed a commit to v8/v8 that referenced this pull request Aug 20, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[platform][posix] Fallback to conservative stack limit on musl
ba4ef8d
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs/node#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
joyeecheung added a commit to targos/node that referenced this pull request Aug 21, 2026
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
2163263
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
joyeecheungand others added 17 commits September 2, 2026 00:17
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
d17d73c
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@targos@joyeecheung
tools: update V8 gypfiles for 14.8
f819b6e
Co-Authored-By: Joyee Cheung <joyeec9h3@gmail.com>
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 14.9
71bee9e
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.0
0f22a95
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.1
20288e7
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
build: disable v8_postmortem_support
cc10b48
Post-mortem libraries should use v8's debug_helper library instead.
@targos@joyeecheung
src: migrate from deprecated xxxV2 APIs
e0c1284
- Set/GetPrototype
- Holder
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
src: migrate from v8::PropertyCallbackInfo<void>
54647f9
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
test: update wpt Wasm jsapi expectations
5431e04
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
test: update test-heapdump-vm-script.js for new version of V8
0376950
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
build: use ICU_UTIL_DATA_STATIC across V8
10b196c
ICU_UTIL_DATA_SHARED had been removed since
https://crrev.com/c/1513615, but Node.js still defined
it and relied on the removed path on Windows, so the ICU
initialization in mksnapshot had been silently failing
since then. https://crrev.com/c/7679153 made the failure
visible so the build started breaking on Windows. Fix it
by always using ICU_UTIL_DATA_STATIC since we already compile
the ICU data statically in.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
src: fix external reference registration for new CFunction lifetime
ac31ae3
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
test: update for new V8 serialization format
a45b843
V8 bumped its wire-format version from 0x0f to 0x10. Update the
expected hex in test-v8-serdes, and derive the v8 header bytes
dynamically in test-runner-v8-deserializer so it tracks future
bumps automatically.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@targos@joyeecheung
test: avoid worker in shared value conveyor test
f554209
V8 no longer supports JSON.parse on worker isolates while the shared
string table is enabled. Since --harmony-struct enables that table and
Node workers parse process.config during bootstrap,
use direct MessageChannel instead of a worker.
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@legendecas@joyeecheung
build: fix cppgc_base perfetto source scraper
e33a7c1
Signed-off-by: Chengzhong Wu <cwu631@bloomberg.net>
@joyeecheung
deps: V8: cherry-pick ba4ef8d72cde
7541bc4
Original commit message:
[platform][posix] Fallback to conservative stack limit on musl
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
Refs: v8/v8@ba4ef8d
@miladfarca@joyeecheung
deps: V8: cherry-pick 811fe8b04203
cd337e7
Original commit message:
Skip regress-498816446-3 when there is not enough memory
Currently causing a test failure on a machine with 8Gb of memory:
```
regress-498816446-3.js:25: RangeError: Array buffer allocation failed
```
Change-Id: I9e0396445c0b870d0070d666f9d6081b93e80f9c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8252113
Commit-Queue: Milad Farazmand <mfarazma@ibm.com>
Reviewed-by: Darius Mercadier <dmercadier@chromium.org>
Cr-Commit-Position: refs/heads/main@{#109426}
Refs: v8/v8@811fe8b
@StefanStojanovic@joyeecheung
build,win: fix
5f18227
Signed-off-by: StefanStojanovic <stefan.stojanovic@janeasystems.com>
@nodejs-github-bot

nodejs-github-bot commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

CI: https://ci.nodejs.org/job/node-test-pull-request/76860/

@aduh95

aduh95 commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Test failing across multiple platforms:

---
duration_ms: 526.097
exitcode: 1
severity: fail
stack: |-
node:internal/assert/utils:146
throw error;
^
AssertionError [ERR_ASSERTION]: The input did not match the regular expression /kMaxReasonableBytes/. Input:
''
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-external-memory-reasonable-size.js:32:10)
at Module._compile (node:internal/modules/cjs/loader:1956:14)
at Object..js (node:internal/modules/cjs/loader:2096:10)
at Module.load (node:internal/modules/cjs/loader:1678:32)
at Module._load (node:internal/modules/cjs/loader:1470:12)
at wrapModuleLoad (node:internal/modules/cjs/loader:261:19)
at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
at node:internal/main/run_main_module:33:47 {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: '',
expected: /kMaxReasonableBytes/,
operator: 'match',
diff: 'simple'
}
Node.js v27.0.0-pre

@targos

targos commented Sep 2, 2026

Copy link
Copy Markdown
MemberAuthor

Just recompiled the branch. On my computer (macOS) it no longer prints the error and stack trace there's just:

➤ out/Debug/node --external-memory-max-reasonable-size=1 -e "new Float64Array(150_000_000)"
fish: Job 1, 'out/Debug/node --external-memor…' terminated by signal SIGTRAP (Trace or breakpoint trap)

@joyeecheung

joyeecheung commented Sep 2, 2026

Copy link
Copy Markdown
Member

Looks like a regression from #65589

@joyeecheung

joyeecheung commented Sep 2, 2026

Copy link
Copy Markdown
Member

Looks like it's caused by https://chromium-review.googlesource.com/c/v8/v8/+/7705483, we should configure V8_LOGGING_LEVEL in gyp so that it prints something when CHECK fails.

@joyeecheung
build: derive V8_LOGGING_LEVEL from dcheck_always_on
5040994
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheungjoyeecheung mentioned this pull request Sep 2, 2026
Open
@joyeecheung

joyeecheung commented Sep 2, 2026

Copy link
Copy Markdown
Member

Pushed #65744 to this branch to check how the CI responds..

@nodejs-github-bot

nodejs-github-bot commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

CI: https://ci.nodejs.org/job/node-test-pull-request/76882/

@Renegade334Renegade334 mentioned this pull request Sep 2, 2026
Open
@eliau2005eliau2005 mentioned this pull request Sep 3, 2026
Open
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

buildIssues and PRs related to Node.js builds or CI infrastructure.dependenciesPRs that add, update, or configure Node.js dependencies.needs-ciPRs that need a full CI run.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

10 participants

@targos@nodejs-github-bot@joyeecheung@richardlau@legendecas@miladfarca@StefanStojanovic@danmcd@aduh95@abmusse
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
deps: update V8 to 15.2 - #65161
Open
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Open
deps: update V8 to 15.2#65161
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Conversation
@targos
@targostargos
commented
Aug 9, 2026

Copy link


Copy Markdown

Member
Refs: #64784
@nodejs-github-bot
nodejs-github-bot
commented
Aug 9, 2026•

edited by targos

Loading

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/gyp
  •  @nodejs/security-wg
  •  @nodejs/v8
@targostargos
changed the title
deps: update V8 to 15.2.124.7deps: update V8 to 15.2Aug 9, 2026
@nodejs-github-botnodejs-github-bot
added

build
Issues and PRs related to Node.js builds or CI infrastructure.
dependencies
PRs that add, update, or configure Node.js dependencies.
needs-ci
PRs that need a full CI run.
labels
Aug 9, 2026
@targostargos
mentioned this pull request
Aug 9, 2026
 Open

@targos
targos
commented
Aug 9, 2026

Copy link


Copy Markdown

MemberAuthor
I guess this is blocked by #64408 (https://github.com/nodejs/node/actions/runs/31307061482/job/93228984418?pr=65161)
@joyeecheung
joyeecheung
commented
Aug 10, 2026

Copy link


Copy Markdown

Member
Uploaded https://chromium-review.googlesource.com/c/v8/v8/+/8223266 to fix the Linux AArch64 build (haven't tested on real Linux AArch64 yet, but that's what the error message suggests)
hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 13, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[simd] Disable SVE implementation of array search for GCC
68cf9ec
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs/node#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
targos pushed a commit
to targos/node
that referenced
this pull request
Aug 13, 2026
@joyeecheung@targos
deps: V8: cherry-pick 68cf9ecd884b
d356533
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@richardlau
richardlau
commented
Aug 13, 2026

Copy link


Copy Markdown

Member
FWIW https://chromium-review.googlesource.com/c/v8/v8/+/8236132 was opened by @sravani1510 to address the AIX build failure that is occurring on our V8 nightly builds.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@nodejs/platform-windows We're hitting a weird error on Windows:
https://github.com/nodejs/node/actions/runs/31699320590/job/94444346312?pr=65161
 Unexpected command-line argument "src/debug/debug-wasm-obects.q", expected a .tq file.
C:\Program Files\Microsoft Visual Studio\18\Enterprise\MSBuild\Microsoft\VC\v180\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for '..\..\out\Release\\torque.exe' exited with code 3. [D:\a\node\node\tools\v8_gypfiles\run_torque.vcxproj]

This wrong path doesn't exist in the code.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@legendecas Can you help with the perfetto build?
@legendecas
legendecas
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
Fixed the perfetto build. But I think the CI is failing for tests in large pages. Likely not related.
@targos
targos
commented
Aug 14, 2026

Copy link


Copy Markdown

MemberAuthor
Thanks. Summary of the remaining issues in GitHub CI:
I'll start a Jenkins CI for more coverage.
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/75841/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark-ubuntu2404-intel-64,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/
@richardlau
richardlau
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
Been talking to @miladfarca about this:
16:01:57 === mjsunit/maglev/regress-498816446-3 ===
16:01:57 --- stderr ---
16:01:57 V8 is running with experimental features enabled. Stability and security will suffer.
16:01:57 --- stdout ---
16:01:57 test/mjsunit/maglev/regress-498816446-3.js:25: RangeError: Array buffer allocation failed
16:01:57 ta = new Int32Array(0xffffffff+1);
16:01:57 ^
16:01:57 RangeError: Array buffer allocation failed
16:01:57 at new ArrayBuffer (<anonymous>)
16:01:57 at new Int32Array (<anonymous>)
16:01:57 at test/mjsunit/maglev/regress-498816446-3.js:25:6
16:01:57 Command: out.gn/s390x.release/d8 --test test/mjsunit/mjsunit.js test/mjsunit/maglev/regress-498816446-3.js --random-seed=-770474680 --nohard-abort --allow-natives-syntax --maglev-object-tracking --maglev
16:01:57 16:01:57 ===
16:01:57 === 1 tests failed
16:01:57 ===
16:01:57 >>> 17287 base tests produced 15072 (87%) non-filtered tests
16:01:57 >>> 15072 tests ran

The Linux ppc64le and s390x machines being tested on have 8GB RAM and this test is allocating 16GB.
@miladfarca
miladfarca
commented
Aug 14, 2026

Copy link


Copy Markdown

Contributor
Patched it here: https://crrev.com/c/8252113

This was referenced Aug 18, 2026
 Open

 Merged

@joyeecheung
joyeecheung
commented
Aug 19, 2026

Copy link


Copy Markdown

Member
For the SEA test failures: they should not have run in the first place. #63751 should fix it.
@joyeecheung
joyeecheung
commented
Aug 20, 2026

Copy link


Copy Markdown

Member
This should fix the alpine failures https://chromium-review.googlesource.com/c/v8/v8/+/8254825
@sxasxa
mentioned this pull request
Aug 20, 2026

Open

hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 20, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[platform][posix] Fallback to conservative stack limit on musl
ba4ef8d
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs/node#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
joyeecheung added a commit
to targos/node
that referenced
this pull request
Aug 21, 2026
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
2163263
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
joyeecheungand others
added 17 commits
September 2, 2026 00:17
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
d17d73c
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@targos@joyeecheung
tools: update V8 gypfiles for 14.8
f819b6e
Co-Authored-By: Joyee Cheung <joyeec9h3@gmail.com>
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 14.9
71bee9e
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.0
0f22a95
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.1
20288e7
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
build: disable v8_postmortem_support
cc10b48
Post-mortem libraries should use v8's debug_helper library instead.
@targos@joyeecheung
src: migrate from deprecated xxxV2 APIs
e0c1284
- Set/GetPrototype
- Holder
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
src: migrate from v8::PropertyCallbackInfo<void>
54647f9
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
test: update wpt Wasm jsapi expectations
5431e04
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
test: update test-heapdump-vm-script.js for new version of V8
0376950
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
build: use ICU_UTIL_DATA_STATIC across V8
10b196c
ICU_UTIL_DATA_SHARED had been removed since
https://crrev.com/c/1513615, but Node.js still defined
it and relied on the removed path on Windows, so the ICU
initialization in mksnapshot had been silently failing
since then. https://crrev.com/c/7679153 made the failure
visible so the build started breaking on Windows. Fix it
by always using ICU_UTIL_DATA_STATIC since we already compile
the ICU data statically in.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
src: fix external reference registration for new CFunction lifetime
ac31ae3
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
test: update for new V8 serialization format
a45b843
V8 bumped its wire-format version from 0x0f to 0x10. Update the
expected hex in test-v8-serdes, and derive the v8 header bytes
dynamically in test-runner-v8-deserializer so it tracks future
bumps automatically.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@targos@joyeecheung
test: avoid worker in shared value conveyor test
f554209
V8 no longer supports JSON.parse on worker isolates while the shared
string table is enabled. Since --harmony-struct enables that table and
Node workers parse process.config during bootstrap,
use direct MessageChannel instead of a worker.
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@legendecas@joyeecheung
build: fix cppgc_base perfetto source scraper
e33a7c1
Signed-off-by: Chengzhong Wu <cwu631@bloomberg.net>
@joyeecheung
deps: V8: cherry-pick ba4ef8d72cde
7541bc4
Original commit message:
[platform][posix] Fallback to conservative stack limit on musl
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
Refs: v8/v8@ba4ef8d
@miladfarca@joyeecheung
deps: V8: cherry-pick 811fe8b04203
cd337e7
Original commit message:
Skip regress-498816446-3 when there is not enough memory
Currently causing a test failure on a machine with 8Gb of memory:
```
regress-498816446-3.js:25: RangeError: Array buffer allocation failed
```
Change-Id: I9e0396445c0b870d0070d666f9d6081b93e80f9c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8252113
Commit-Queue: Milad Farazmand <mfarazma@ibm.com>
Reviewed-by: Darius Mercadier <dmercadier@chromium.org>
Cr-Commit-Position: refs/heads/main@{#109426}
Refs: v8/v8@811fe8b
@StefanStojanovic@joyeecheung
build,win: fix
5f18227
Signed-off-by: StefanStojanovic <stefan.stojanovic@janeasystems.com>
@nodejs-github-bot
nodejs-github-bot
commented
Sep 1, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76860/
@aduh95
aduh95
commented
Sep 2, 2026

Copy link


Copy Markdown

Contributor
Test failing across multiple platforms:
---
duration_ms: 526.097
exitcode: 1
severity: fail
stack: |-
node:internal/assert/utils:146
throw error;
^
AssertionError [ERR_ASSERTION]: The input did not match the regular expression /kMaxReasonableBytes/. Input:
''
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-external-memory-reasonable-size.js:32:10)
at Module._compile (node:internal/modules/cjs/loader:1956:14)
at Object..js (node:internal/modules/cjs/loader:2096:10)
at Module.load (node:internal/modules/cjs/loader:1678:32)
at Module._load (node:internal/modules/cjs/loader:1470:12)
at wrapModuleLoad (node:internal/modules/cjs/loader:261:19)
at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
at node:internal/main/run_main_module:33:47 {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: '',
expected: /kMaxReasonableBytes/,
operator: 'match',
diff: 'simple'
}
Node.js v27.0.0-pre

@targos
targos
commented
Sep 2, 2026

Copy link


Copy Markdown

MemberAuthor
Just recompiled the branch. On my computer (macOS) it no longer prints the error and stack trace there's just:
➤ out/Debug/node --external-memory-max-reasonable-size=1 -e "new Float64Array(150_000_000)"
fish: Job 1, 'out/Debug/node --external-memor…' terminated by signal SIGTRAP (Trace or breakpoint trap)

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like a regression from #65589
@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like it's caused by https://chromium-review.googlesource.com/c/v8/v8/+/7705483, we should configure V8_LOGGING_LEVEL in gyp so that it prints something when CHECK fails.
@joyeecheung
build: derive V8_LOGGING_LEVEL from dcheck_always_on
5040994
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheungjoyeecheung
mentioned this pull request
Sep 2, 2026
 Open

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Pushed #65744 to this branch to check how the CI responds..
@nodejs-github-bot
nodejs-github-bot
commented
Sep 2, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76882/
@Renegade334Renegade334
mentioned this pull request
Sep 2, 2026
 Open

@eliau2005eliau2005
mentioned this pull request
Sep 3, 2026

Open

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

buildIssues and PRs related to Node.js builds or CI infrastructure.dependenciesPRs that add, update, or configure Node.js dependencies.needs-ciPRs that need a full CI run.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

10 participants

@targos@nodejs-github-bot@joyeecheung@richardlau@legendecas@miladfarca@StefanStojanovic@danmcd@aduh95@abmusse

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
deps: update V8 to 15.2 - #65161
Open
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Open
deps: update V8 to 15.2#65161
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Conversation
@targos
@targostargos
commented
Aug 9, 2026

Copy link


Copy Markdown

Member
Refs: #64784
@nodejs-github-bot
nodejs-github-bot
commented
Aug 9, 2026•

edited by targos

Loading

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/gyp
  •  @nodejs/security-wg
  •  @nodejs/v8
@targostargos
changed the title
deps: update V8 to 15.2.124.7deps: update V8 to 15.2Aug 9, 2026
@nodejs-github-botnodejs-github-bot
added

build
Issues and PRs related to Node.js builds or CI infrastructure.
dependencies
PRs that add, update, or configure Node.js dependencies.
needs-ci
PRs that need a full CI run.
labels
Aug 9, 2026
@targostargos
mentioned this pull request
Aug 9, 2026
 Open

@targos
targos
commented
Aug 9, 2026

Copy link


Copy Markdown

MemberAuthor
I guess this is blocked by #64408 (https://github.com/nodejs/node/actions/runs/31307061482/job/93228984418?pr=65161)
@joyeecheung
joyeecheung
commented
Aug 10, 2026

Copy link


Copy Markdown

Member
Uploaded https://chromium-review.googlesource.com/c/v8/v8/+/8223266 to fix the Linux AArch64 build (haven't tested on real Linux AArch64 yet, but that's what the error message suggests)
hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 13, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[simd] Disable SVE implementation of array search for GCC
68cf9ec
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs/node#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
targos pushed a commit
to targos/node
that referenced
this pull request
Aug 13, 2026
@joyeecheung@targos
deps: V8: cherry-pick 68cf9ecd884b
d356533
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@richardlau
richardlau
commented
Aug 13, 2026

Copy link


Copy Markdown

Member
FWIW https://chromium-review.googlesource.com/c/v8/v8/+/8236132 was opened by @sravani1510 to address the AIX build failure that is occurring on our V8 nightly builds.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@nodejs/platform-windows We're hitting a weird error on Windows:
https://github.com/nodejs/node/actions/runs/31699320590/job/94444346312?pr=65161
 Unexpected command-line argument "src/debug/debug-wasm-obects.q", expected a .tq file.
C:\Program Files\Microsoft Visual Studio\18\Enterprise\MSBuild\Microsoft\VC\v180\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for '..\..\out\Release\\torque.exe' exited with code 3. [D:\a\node\node\tools\v8_gypfiles\run_torque.vcxproj]

This wrong path doesn't exist in the code.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@legendecas Can you help with the perfetto build?
@legendecas
legendecas
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
Fixed the perfetto build. But I think the CI is failing for tests in large pages. Likely not related.
@targos
targos
commented
Aug 14, 2026

Copy link


Copy Markdown

MemberAuthor
Thanks. Summary of the remaining issues in GitHub CI:
I'll start a Jenkins CI for more coverage.
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/75841/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark-ubuntu2404-intel-64,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/
@richardlau
richardlau
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
Been talking to @miladfarca about this:
16:01:57 === mjsunit/maglev/regress-498816446-3 ===
16:01:57 --- stderr ---
16:01:57 V8 is running with experimental features enabled. Stability and security will suffer.
16:01:57 --- stdout ---
16:01:57 test/mjsunit/maglev/regress-498816446-3.js:25: RangeError: Array buffer allocation failed
16:01:57 ta = new Int32Array(0xffffffff+1);
16:01:57 ^
16:01:57 RangeError: Array buffer allocation failed
16:01:57 at new ArrayBuffer (<anonymous>)
16:01:57 at new Int32Array (<anonymous>)
16:01:57 at test/mjsunit/maglev/regress-498816446-3.js:25:6
16:01:57 Command: out.gn/s390x.release/d8 --test test/mjsunit/mjsunit.js test/mjsunit/maglev/regress-498816446-3.js --random-seed=-770474680 --nohard-abort --allow-natives-syntax --maglev-object-tracking --maglev
16:01:57 16:01:57 ===
16:01:57 === 1 tests failed
16:01:57 ===
16:01:57 >>> 17287 base tests produced 15072 (87%) non-filtered tests
16:01:57 >>> 15072 tests ran

The Linux ppc64le and s390x machines being tested on have 8GB RAM and this test is allocating 16GB.
@miladfarca
miladfarca
commented
Aug 14, 2026

Copy link


Copy Markdown

Contributor
Patched it here: https://crrev.com/c/8252113

This was referenced Aug 18, 2026
 Open

 Merged

@joyeecheung
joyeecheung
commented
Aug 19, 2026

Copy link


Copy Markdown

Member
For the SEA test failures: they should not have run in the first place. #63751 should fix it.
@joyeecheung
joyeecheung
commented
Aug 20, 2026

Copy link


Copy Markdown

Member
This should fix the alpine failures https://chromium-review.googlesource.com/c/v8/v8/+/8254825
@sxasxa
mentioned this pull request
Aug 20, 2026

Open

hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 20, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[platform][posix] Fallback to conservative stack limit on musl
ba4ef8d
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs/node#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
joyeecheung added a commit
to targos/node
that referenced
this pull request
Aug 21, 2026
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
2163263
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
joyeecheungand others
added 17 commits
September 2, 2026 00:17
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
d17d73c
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@targos@joyeecheung
tools: update V8 gypfiles for 14.8
f819b6e
Co-Authored-By: Joyee Cheung <joyeec9h3@gmail.com>
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 14.9
71bee9e
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.0
0f22a95
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.1
20288e7
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
build: disable v8_postmortem_support
cc10b48
Post-mortem libraries should use v8's debug_helper library instead.
@targos@joyeecheung
src: migrate from deprecated xxxV2 APIs
e0c1284
- Set/GetPrototype
- Holder
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
src: migrate from v8::PropertyCallbackInfo<void>
54647f9
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
test: update wpt Wasm jsapi expectations
5431e04
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
test: update test-heapdump-vm-script.js for new version of V8
0376950
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
build: use ICU_UTIL_DATA_STATIC across V8
10b196c
ICU_UTIL_DATA_SHARED had been removed since
https://crrev.com/c/1513615, but Node.js still defined
it and relied on the removed path on Windows, so the ICU
initialization in mksnapshot had been silently failing
since then. https://crrev.com/c/7679153 made the failure
visible so the build started breaking on Windows. Fix it
by always using ICU_UTIL_DATA_STATIC since we already compile
the ICU data statically in.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
src: fix external reference registration for new CFunction lifetime
ac31ae3
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
test: update for new V8 serialization format
a45b843
V8 bumped its wire-format version from 0x0f to 0x10. Update the
expected hex in test-v8-serdes, and derive the v8 header bytes
dynamically in test-runner-v8-deserializer so it tracks future
bumps automatically.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@targos@joyeecheung
test: avoid worker in shared value conveyor test
f554209
V8 no longer supports JSON.parse on worker isolates while the shared
string table is enabled. Since --harmony-struct enables that table and
Node workers parse process.config during bootstrap,
use direct MessageChannel instead of a worker.
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@legendecas@joyeecheung
build: fix cppgc_base perfetto source scraper
e33a7c1
Signed-off-by: Chengzhong Wu <cwu631@bloomberg.net>
@joyeecheung
deps: V8: cherry-pick ba4ef8d72cde
7541bc4
Original commit message:
[platform][posix] Fallback to conservative stack limit on musl
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
Refs: v8/v8@ba4ef8d
@miladfarca@joyeecheung
deps: V8: cherry-pick 811fe8b04203
cd337e7
Original commit message:
Skip regress-498816446-3 when there is not enough memory
Currently causing a test failure on a machine with 8Gb of memory:
```
regress-498816446-3.js:25: RangeError: Array buffer allocation failed
```
Change-Id: I9e0396445c0b870d0070d666f9d6081b93e80f9c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8252113
Commit-Queue: Milad Farazmand <mfarazma@ibm.com>
Reviewed-by: Darius Mercadier <dmercadier@chromium.org>
Cr-Commit-Position: refs/heads/main@{#109426}
Refs: v8/v8@811fe8b
@StefanStojanovic@joyeecheung
build,win: fix
5f18227
Signed-off-by: StefanStojanovic <stefan.stojanovic@janeasystems.com>
@nodejs-github-bot
nodejs-github-bot
commented
Sep 1, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76860/
@aduh95
aduh95
commented
Sep 2, 2026

Copy link


Copy Markdown

Contributor
Test failing across multiple platforms:
---
duration_ms: 526.097
exitcode: 1
severity: fail
stack: |-
node:internal/assert/utils:146
throw error;
^
AssertionError [ERR_ASSERTION]: The input did not match the regular expression /kMaxReasonableBytes/. Input:
''
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-external-memory-reasonable-size.js:32:10)
at Module._compile (node:internal/modules/cjs/loader:1956:14)
at Object..js (node:internal/modules/cjs/loader:2096:10)
at Module.load (node:internal/modules/cjs/loader:1678:32)
at Module._load (node:internal/modules/cjs/loader:1470:12)
at wrapModuleLoad (node:internal/modules/cjs/loader:261:19)
at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
at node:internal/main/run_main_module:33:47 {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: '',
expected: /kMaxReasonableBytes/,
operator: 'match',
diff: 'simple'
}
Node.js v27.0.0-pre

@targos
targos
commented
Sep 2, 2026

Copy link


Copy Markdown

MemberAuthor
Just recompiled the branch. On my computer (macOS) it no longer prints the error and stack trace there's just:
➤ out/Debug/node --external-memory-max-reasonable-size=1 -e "new Float64Array(150_000_000)"
fish: Job 1, 'out/Debug/node --external-memor…' terminated by signal SIGTRAP (Trace or breakpoint trap)

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like a regression from #65589
@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like it's caused by https://chromium-review.googlesource.com/c/v8/v8/+/7705483, we should configure V8_LOGGING_LEVEL in gyp so that it prints something when CHECK fails.
@joyeecheung
build: derive V8_LOGGING_LEVEL from dcheck_always_on
5040994
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheungjoyeecheung
mentioned this pull request
Sep 2, 2026
 Open

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Pushed #65744 to this branch to check how the CI responds..
@nodejs-github-bot
nodejs-github-bot
commented
Sep 2, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76882/
@Renegade334Renegade334
mentioned this pull request
Sep 2, 2026
 Open

@eliau2005eliau2005
mentioned this pull request
Sep 3, 2026

Open

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

buildIssues and PRs related to Node.js builds or CI infrastructure.dependenciesPRs that add, update, or configure Node.js dependencies.needs-ciPRs that need a full CI run.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

10 participants

@targos@nodejs-github-bot@joyeecheung@richardlau@legendecas@miladfarca@StefanStojanovic@danmcd@aduh95@abmusse

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
deps: update V8 to 15.2 - #65161
Open
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Open
deps: update V8 to 15.2#65161
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Conversation
@targos
@targostargos
commented
Aug 9, 2026

Copy link


Copy Markdown

Member
Refs: #64784
@nodejs-github-bot
nodejs-github-bot
commented
Aug 9, 2026•

edited by targos

Loading

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/gyp
  •  @nodejs/security-wg
  •  @nodejs/v8
@targostargos
changed the title
deps: update V8 to 15.2.124.7deps: update V8 to 15.2Aug 9, 2026
@nodejs-github-botnodejs-github-bot
added

build
Issues and PRs related to Node.js builds or CI infrastructure.
dependencies
PRs that add, update, or configure Node.js dependencies.
needs-ci
PRs that need a full CI run.
labels
Aug 9, 2026
@targostargos
mentioned this pull request
Aug 9, 2026
 Open

@targos
targos
commented
Aug 9, 2026

Copy link


Copy Markdown

MemberAuthor
I guess this is blocked by #64408 (https://github.com/nodejs/node/actions/runs/31307061482/job/93228984418?pr=65161)
@joyeecheung
joyeecheung
commented
Aug 10, 2026

Copy link


Copy Markdown

Member
Uploaded https://chromium-review.googlesource.com/c/v8/v8/+/8223266 to fix the Linux AArch64 build (haven't tested on real Linux AArch64 yet, but that's what the error message suggests)
hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 13, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[simd] Disable SVE implementation of array search for GCC
68cf9ec
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs/node#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
targos pushed a commit
to targos/node
that referenced
this pull request
Aug 13, 2026
@joyeecheung@targos
deps: V8: cherry-pick 68cf9ecd884b
d356533
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@richardlau
richardlau
commented
Aug 13, 2026

Copy link


Copy Markdown

Member
FWIW https://chromium-review.googlesource.com/c/v8/v8/+/8236132 was opened by @sravani1510 to address the AIX build failure that is occurring on our V8 nightly builds.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@nodejs/platform-windows We're hitting a weird error on Windows:
https://github.com/nodejs/node/actions/runs/31699320590/job/94444346312?pr=65161
 Unexpected command-line argument "src/debug/debug-wasm-obects.q", expected a .tq file.
C:\Program Files\Microsoft Visual Studio\18\Enterprise\MSBuild\Microsoft\VC\v180\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for '..\..\out\Release\\torque.exe' exited with code 3. [D:\a\node\node\tools\v8_gypfiles\run_torque.vcxproj]

This wrong path doesn't exist in the code.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@legendecas Can you help with the perfetto build?
@legendecas
legendecas
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
Fixed the perfetto build. But I think the CI is failing for tests in large pages. Likely not related.
@targos
targos
commented
Aug 14, 2026

Copy link


Copy Markdown

MemberAuthor
Thanks. Summary of the remaining issues in GitHub CI:
I'll start a Jenkins CI for more coverage.
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/75841/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark-ubuntu2404-intel-64,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/
@richardlau
richardlau
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
Been talking to @miladfarca about this:
16:01:57 === mjsunit/maglev/regress-498816446-3 ===
16:01:57 --- stderr ---
16:01:57 V8 is running with experimental features enabled. Stability and security will suffer.
16:01:57 --- stdout ---
16:01:57 test/mjsunit/maglev/regress-498816446-3.js:25: RangeError: Array buffer allocation failed
16:01:57 ta = new Int32Array(0xffffffff+1);
16:01:57 ^
16:01:57 RangeError: Array buffer allocation failed
16:01:57 at new ArrayBuffer (<anonymous>)
16:01:57 at new Int32Array (<anonymous>)
16:01:57 at test/mjsunit/maglev/regress-498816446-3.js:25:6
16:01:57 Command: out.gn/s390x.release/d8 --test test/mjsunit/mjsunit.js test/mjsunit/maglev/regress-498816446-3.js --random-seed=-770474680 --nohard-abort --allow-natives-syntax --maglev-object-tracking --maglev
16:01:57 16:01:57 ===
16:01:57 === 1 tests failed
16:01:57 ===
16:01:57 >>> 17287 base tests produced 15072 (87%) non-filtered tests
16:01:57 >>> 15072 tests ran

The Linux ppc64le and s390x machines being tested on have 8GB RAM and this test is allocating 16GB.
@miladfarca
miladfarca
commented
Aug 14, 2026

Copy link


Copy Markdown

Contributor
Patched it here: https://crrev.com/c/8252113

This was referenced Aug 18, 2026
 Open

 Merged

@joyeecheung
joyeecheung
commented
Aug 19, 2026

Copy link


Copy Markdown

Member
For the SEA test failures: they should not have run in the first place. #63751 should fix it.
@joyeecheung
joyeecheung
commented
Aug 20, 2026

Copy link


Copy Markdown

Member
This should fix the alpine failures https://chromium-review.googlesource.com/c/v8/v8/+/8254825
@sxasxa
mentioned this pull request
Aug 20, 2026

Open

hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 20, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[platform][posix] Fallback to conservative stack limit on musl
ba4ef8d
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs/node#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
joyeecheung added a commit
to targos/node
that referenced
this pull request
Aug 21, 2026
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
2163263
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
joyeecheungand others
added 17 commits
September 2, 2026 00:17
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
d17d73c
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@targos@joyeecheung
tools: update V8 gypfiles for 14.8
f819b6e
Co-Authored-By: Joyee Cheung <joyeec9h3@gmail.com>
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 14.9
71bee9e
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.0
0f22a95
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.1
20288e7
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
build: disable v8_postmortem_support
cc10b48
Post-mortem libraries should use v8's debug_helper library instead.
@targos@joyeecheung
src: migrate from deprecated xxxV2 APIs
e0c1284
- Set/GetPrototype
- Holder
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
src: migrate from v8::PropertyCallbackInfo<void>
54647f9
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
test: update wpt Wasm jsapi expectations
5431e04
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
test: update test-heapdump-vm-script.js for new version of V8
0376950
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
build: use ICU_UTIL_DATA_STATIC across V8
10b196c
ICU_UTIL_DATA_SHARED had been removed since
https://crrev.com/c/1513615, but Node.js still defined
it and relied on the removed path on Windows, so the ICU
initialization in mksnapshot had been silently failing
since then. https://crrev.com/c/7679153 made the failure
visible so the build started breaking on Windows. Fix it
by always using ICU_UTIL_DATA_STATIC since we already compile
the ICU data statically in.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
src: fix external reference registration for new CFunction lifetime
ac31ae3
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
test: update for new V8 serialization format
a45b843
V8 bumped its wire-format version from 0x0f to 0x10. Update the
expected hex in test-v8-serdes, and derive the v8 header bytes
dynamically in test-runner-v8-deserializer so it tracks future
bumps automatically.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@targos@joyeecheung
test: avoid worker in shared value conveyor test
f554209
V8 no longer supports JSON.parse on worker isolates while the shared
string table is enabled. Since --harmony-struct enables that table and
Node workers parse process.config during bootstrap,
use direct MessageChannel instead of a worker.
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@legendecas@joyeecheung
build: fix cppgc_base perfetto source scraper
e33a7c1
Signed-off-by: Chengzhong Wu <cwu631@bloomberg.net>
@joyeecheung
deps: V8: cherry-pick ba4ef8d72cde
7541bc4
Original commit message:
[platform][posix] Fallback to conservative stack limit on musl
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
Refs: v8/v8@ba4ef8d
@miladfarca@joyeecheung
deps: V8: cherry-pick 811fe8b04203
cd337e7
Original commit message:
Skip regress-498816446-3 when there is not enough memory
Currently causing a test failure on a machine with 8Gb of memory:
```
regress-498816446-3.js:25: RangeError: Array buffer allocation failed
```
Change-Id: I9e0396445c0b870d0070d666f9d6081b93e80f9c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8252113
Commit-Queue: Milad Farazmand <mfarazma@ibm.com>
Reviewed-by: Darius Mercadier <dmercadier@chromium.org>
Cr-Commit-Position: refs/heads/main@{#109426}
Refs: v8/v8@811fe8b
@StefanStojanovic@joyeecheung
build,win: fix
5f18227
Signed-off-by: StefanStojanovic <stefan.stojanovic@janeasystems.com>
@nodejs-github-bot
nodejs-github-bot
commented
Sep 1, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76860/
@aduh95
aduh95
commented
Sep 2, 2026

Copy link


Copy Markdown

Contributor
Test failing across multiple platforms:
---
duration_ms: 526.097
exitcode: 1
severity: fail
stack: |-
node:internal/assert/utils:146
throw error;
^
AssertionError [ERR_ASSERTION]: The input did not match the regular expression /kMaxReasonableBytes/. Input:
''
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-external-memory-reasonable-size.js:32:10)
at Module._compile (node:internal/modules/cjs/loader:1956:14)
at Object..js (node:internal/modules/cjs/loader:2096:10)
at Module.load (node:internal/modules/cjs/loader:1678:32)
at Module._load (node:internal/modules/cjs/loader:1470:12)
at wrapModuleLoad (node:internal/modules/cjs/loader:261:19)
at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
at node:internal/main/run_main_module:33:47 {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: '',
expected: /kMaxReasonableBytes/,
operator: 'match',
diff: 'simple'
}
Node.js v27.0.0-pre

@targos
targos
commented
Sep 2, 2026

Copy link


Copy Markdown

MemberAuthor
Just recompiled the branch. On my computer (macOS) it no longer prints the error and stack trace there's just:
➤ out/Debug/node --external-memory-max-reasonable-size=1 -e "new Float64Array(150_000_000)"
fish: Job 1, 'out/Debug/node --external-memor…' terminated by signal SIGTRAP (Trace or breakpoint trap)

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like a regression from #65589
@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like it's caused by https://chromium-review.googlesource.com/c/v8/v8/+/7705483, we should configure V8_LOGGING_LEVEL in gyp so that it prints something when CHECK fails.
@joyeecheung
build: derive V8_LOGGING_LEVEL from dcheck_always_on
5040994
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheungjoyeecheung
mentioned this pull request
Sep 2, 2026
 Open

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Pushed #65744 to this branch to check how the CI responds..
@nodejs-github-bot
nodejs-github-bot
commented
Sep 2, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76882/
@Renegade334Renegade334
mentioned this pull request
Sep 2, 2026
 Open

@eliau2005eliau2005
mentioned this pull request
Sep 3, 2026

Open

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

buildIssues and PRs related to Node.js builds or CI infrastructure.dependenciesPRs that add, update, or configure Node.js dependencies.needs-ciPRs that need a full CI run.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

10 participants

@targos@nodejs-github-bot@joyeecheung@richardlau@legendecas@miladfarca@StefanStojanovic@danmcd@aduh95@abmusse

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
deps: update V8 to 15.2 - #65161
Open
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Open
deps: update V8 to 15.2#65161
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Conversation
@targos
@targostargos
commented
Aug 9, 2026

Copy link


Copy Markdown

Member
Refs: #64784
@nodejs-github-bot
nodejs-github-bot
commented
Aug 9, 2026•

edited by targos

Loading

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/gyp
  •  @nodejs/security-wg
  •  @nodejs/v8
@targostargos
changed the title
deps: update V8 to 15.2.124.7deps: update V8 to 15.2Aug 9, 2026
@nodejs-github-botnodejs-github-bot
added

build
Issues and PRs related to Node.js builds or CI infrastructure.
dependencies
PRs that add, update, or configure Node.js dependencies.
needs-ci
PRs that need a full CI run.
labels
Aug 9, 2026
@targostargos
mentioned this pull request
Aug 9, 2026
 Open

@targos
targos
commented
Aug 9, 2026

Copy link


Copy Markdown

MemberAuthor
I guess this is blocked by #64408 (https://github.com/nodejs/node/actions/runs/31307061482/job/93228984418?pr=65161)
@joyeecheung
joyeecheung
commented
Aug 10, 2026

Copy link


Copy Markdown

Member
Uploaded https://chromium-review.googlesource.com/c/v8/v8/+/8223266 to fix the Linux AArch64 build (haven't tested on real Linux AArch64 yet, but that's what the error message suggests)
hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 13, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[simd] Disable SVE implementation of array search for GCC
68cf9ec
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs/node#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
targos pushed a commit
to targos/node
that referenced
this pull request
Aug 13, 2026
@joyeecheung@targos
deps: V8: cherry-pick 68cf9ecd884b
d356533
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@richardlau
richardlau
commented
Aug 13, 2026

Copy link


Copy Markdown

Member
FWIW https://chromium-review.googlesource.com/c/v8/v8/+/8236132 was opened by @sravani1510 to address the AIX build failure that is occurring on our V8 nightly builds.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@nodejs/platform-windows We're hitting a weird error on Windows:
https://github.com/nodejs/node/actions/runs/31699320590/job/94444346312?pr=65161
 Unexpected command-line argument "src/debug/debug-wasm-obects.q", expected a .tq file.
C:\Program Files\Microsoft Visual Studio\18\Enterprise\MSBuild\Microsoft\VC\v180\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for '..\..\out\Release\\torque.exe' exited with code 3. [D:\a\node\node\tools\v8_gypfiles\run_torque.vcxproj]

This wrong path doesn't exist in the code.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@legendecas Can you help with the perfetto build?
@legendecas
legendecas
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
Fixed the perfetto build. But I think the CI is failing for tests in large pages. Likely not related.
@targos
targos
commented
Aug 14, 2026

Copy link


Copy Markdown

MemberAuthor
Thanks. Summary of the remaining issues in GitHub CI:
I'll start a Jenkins CI for more coverage.
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/75841/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark-ubuntu2404-intel-64,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/
@richardlau
richardlau
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
Been talking to @miladfarca about this:
16:01:57 === mjsunit/maglev/regress-498816446-3 ===
16:01:57 --- stderr ---
16:01:57 V8 is running with experimental features enabled. Stability and security will suffer.
16:01:57 --- stdout ---
16:01:57 test/mjsunit/maglev/regress-498816446-3.js:25: RangeError: Array buffer allocation failed
16:01:57 ta = new Int32Array(0xffffffff+1);
16:01:57 ^
16:01:57 RangeError: Array buffer allocation failed
16:01:57 at new ArrayBuffer (<anonymous>)
16:01:57 at new Int32Array (<anonymous>)
16:01:57 at test/mjsunit/maglev/regress-498816446-3.js:25:6
16:01:57 Command: out.gn/s390x.release/d8 --test test/mjsunit/mjsunit.js test/mjsunit/maglev/regress-498816446-3.js --random-seed=-770474680 --nohard-abort --allow-natives-syntax --maglev-object-tracking --maglev
16:01:57 16:01:57 ===
16:01:57 === 1 tests failed
16:01:57 ===
16:01:57 >>> 17287 base tests produced 15072 (87%) non-filtered tests
16:01:57 >>> 15072 tests ran

The Linux ppc64le and s390x machines being tested on have 8GB RAM and this test is allocating 16GB.
@miladfarca
miladfarca
commented
Aug 14, 2026

Copy link


Copy Markdown

Contributor
Patched it here: https://crrev.com/c/8252113

This was referenced Aug 18, 2026
 Open

 Merged

@joyeecheung
joyeecheung
commented
Aug 19, 2026

Copy link


Copy Markdown

Member
For the SEA test failures: they should not have run in the first place. #63751 should fix it.
@joyeecheung
joyeecheung
commented
Aug 20, 2026

Copy link


Copy Markdown

Member
This should fix the alpine failures https://chromium-review.googlesource.com/c/v8/v8/+/8254825
@sxasxa
mentioned this pull request
Aug 20, 2026

Open

hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 20, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[platform][posix] Fallback to conservative stack limit on musl
ba4ef8d
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs/node#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
joyeecheung added a commit
to targos/node
that referenced
this pull request
Aug 21, 2026
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
2163263
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
joyeecheungand others
added 17 commits
September 2, 2026 00:17
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
d17d73c
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@targos@joyeecheung
tools: update V8 gypfiles for 14.8
f819b6e
Co-Authored-By: Joyee Cheung <joyeec9h3@gmail.com>
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 14.9
71bee9e
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.0
0f22a95
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.1
20288e7
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
build: disable v8_postmortem_support
cc10b48
Post-mortem libraries should use v8's debug_helper library instead.
@targos@joyeecheung
src: migrate from deprecated xxxV2 APIs
e0c1284
- Set/GetPrototype
- Holder
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
src: migrate from v8::PropertyCallbackInfo<void>
54647f9
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
test: update wpt Wasm jsapi expectations
5431e04
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
test: update test-heapdump-vm-script.js for new version of V8
0376950
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
build: use ICU_UTIL_DATA_STATIC across V8
10b196c
ICU_UTIL_DATA_SHARED had been removed since
https://crrev.com/c/1513615, but Node.js still defined
it and relied on the removed path on Windows, so the ICU
initialization in mksnapshot had been silently failing
since then. https://crrev.com/c/7679153 made the failure
visible so the build started breaking on Windows. Fix it
by always using ICU_UTIL_DATA_STATIC since we already compile
the ICU data statically in.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
src: fix external reference registration for new CFunction lifetime
ac31ae3
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
test: update for new V8 serialization format
a45b843
V8 bumped its wire-format version from 0x0f to 0x10. Update the
expected hex in test-v8-serdes, and derive the v8 header bytes
dynamically in test-runner-v8-deserializer so it tracks future
bumps automatically.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@targos@joyeecheung
test: avoid worker in shared value conveyor test
f554209
V8 no longer supports JSON.parse on worker isolates while the shared
string table is enabled. Since --harmony-struct enables that table and
Node workers parse process.config during bootstrap,
use direct MessageChannel instead of a worker.
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@legendecas@joyeecheung
build: fix cppgc_base perfetto source scraper
e33a7c1
Signed-off-by: Chengzhong Wu <cwu631@bloomberg.net>
@joyeecheung
deps: V8: cherry-pick ba4ef8d72cde
7541bc4
Original commit message:
[platform][posix] Fallback to conservative stack limit on musl
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
Refs: v8/v8@ba4ef8d
@miladfarca@joyeecheung
deps: V8: cherry-pick 811fe8b04203
cd337e7
Original commit message:
Skip regress-498816446-3 when there is not enough memory
Currently causing a test failure on a machine with 8Gb of memory:
```
regress-498816446-3.js:25: RangeError: Array buffer allocation failed
```
Change-Id: I9e0396445c0b870d0070d666f9d6081b93e80f9c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8252113
Commit-Queue: Milad Farazmand <mfarazma@ibm.com>
Reviewed-by: Darius Mercadier <dmercadier@chromium.org>
Cr-Commit-Position: refs/heads/main@{#109426}
Refs: v8/v8@811fe8b
@StefanStojanovic@joyeecheung
build,win: fix
5f18227
Signed-off-by: StefanStojanovic <stefan.stojanovic@janeasystems.com>
@nodejs-github-bot
nodejs-github-bot
commented
Sep 1, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76860/
@aduh95
aduh95
commented
Sep 2, 2026

Copy link


Copy Markdown

Contributor
Test failing across multiple platforms:
---
duration_ms: 526.097
exitcode: 1
severity: fail
stack: |-
node:internal/assert/utils:146
throw error;
^
AssertionError [ERR_ASSERTION]: The input did not match the regular expression /kMaxReasonableBytes/. Input:
''
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-external-memory-reasonable-size.js:32:10)
at Module._compile (node:internal/modules/cjs/loader:1956:14)
at Object..js (node:internal/modules/cjs/loader:2096:10)
at Module.load (node:internal/modules/cjs/loader:1678:32)
at Module._load (node:internal/modules/cjs/loader:1470:12)
at wrapModuleLoad (node:internal/modules/cjs/loader:261:19)
at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
at node:internal/main/run_main_module:33:47 {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: '',
expected: /kMaxReasonableBytes/,
operator: 'match',
diff: 'simple'
}
Node.js v27.0.0-pre

@targos
targos
commented
Sep 2, 2026

Copy link


Copy Markdown

MemberAuthor
Just recompiled the branch. On my computer (macOS) it no longer prints the error and stack trace there's just:
➤ out/Debug/node --external-memory-max-reasonable-size=1 -e "new Float64Array(150_000_000)"
fish: Job 1, 'out/Debug/node --external-memor…' terminated by signal SIGTRAP (Trace or breakpoint trap)

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like a regression from #65589
@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like it's caused by https://chromium-review.googlesource.com/c/v8/v8/+/7705483, we should configure V8_LOGGING_LEVEL in gyp so that it prints something when CHECK fails.
@joyeecheung
build: derive V8_LOGGING_LEVEL from dcheck_always_on
5040994
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheungjoyeecheung
mentioned this pull request
Sep 2, 2026
 Open

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Pushed #65744 to this branch to check how the CI responds..
@nodejs-github-bot
nodejs-github-bot
commented
Sep 2, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76882/
@Renegade334Renegade334
mentioned this pull request
Sep 2, 2026
 Open

@eliau2005eliau2005
mentioned this pull request
Sep 3, 2026

Open

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

buildIssues and PRs related to Node.js builds or CI infrastructure.dependenciesPRs that add, update, or configure Node.js dependencies.needs-ciPRs that need a full CI run.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

10 participants

@targos@nodejs-github-bot@joyeecheung@richardlau@legendecas@miladfarca@StefanStojanovic@danmcd@aduh95@abmusse

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
deps: update V8 to 15.2 - #65161
Open
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Open
deps: update V8 to 15.2#65161
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Conversation
@targos
@targostargos
commented
Aug 9, 2026

Copy link


Copy Markdown

Member
Refs: #64784
@nodejs-github-bot
nodejs-github-bot
commented
Aug 9, 2026•

edited by targos

Loading

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/gyp
  •  @nodejs/security-wg
  •  @nodejs/v8
@targostargos
changed the title
deps: update V8 to 15.2.124.7deps: update V8 to 15.2Aug 9, 2026
@nodejs-github-botnodejs-github-bot
added

build
Issues and PRs related to Node.js builds or CI infrastructure.
dependencies
PRs that add, update, or configure Node.js dependencies.
needs-ci
PRs that need a full CI run.
labels
Aug 9, 2026
@targostargos
mentioned this pull request
Aug 9, 2026
 Open

@targos
targos
commented
Aug 9, 2026

Copy link


Copy Markdown

MemberAuthor
I guess this is blocked by #64408 (https://github.com/nodejs/node/actions/runs/31307061482/job/93228984418?pr=65161)
@joyeecheung
joyeecheung
commented
Aug 10, 2026

Copy link


Copy Markdown

Member
Uploaded https://chromium-review.googlesource.com/c/v8/v8/+/8223266 to fix the Linux AArch64 build (haven't tested on real Linux AArch64 yet, but that's what the error message suggests)
hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 13, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[simd] Disable SVE implementation of array search for GCC
68cf9ec
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs/node#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
targos pushed a commit
to targos/node
that referenced
this pull request
Aug 13, 2026
@joyeecheung@targos
deps: V8: cherry-pick 68cf9ecd884b
d356533
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@richardlau
richardlau
commented
Aug 13, 2026

Copy link


Copy Markdown

Member
FWIW https://chromium-review.googlesource.com/c/v8/v8/+/8236132 was opened by @sravani1510 to address the AIX build failure that is occurring on our V8 nightly builds.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@nodejs/platform-windows We're hitting a weird error on Windows:
https://github.com/nodejs/node/actions/runs/31699320590/job/94444346312?pr=65161
 Unexpected command-line argument "src/debug/debug-wasm-obects.q", expected a .tq file.
C:\Program Files\Microsoft Visual Studio\18\Enterprise\MSBuild\Microsoft\VC\v180\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for '..\..\out\Release\\torque.exe' exited with code 3. [D:\a\node\node\tools\v8_gypfiles\run_torque.vcxproj]

This wrong path doesn't exist in the code.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@legendecas Can you help with the perfetto build?
@legendecas
legendecas
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
Fixed the perfetto build. But I think the CI is failing for tests in large pages. Likely not related.
@targos
targos
commented
Aug 14, 2026

Copy link


Copy Markdown

MemberAuthor
Thanks. Summary of the remaining issues in GitHub CI:
I'll start a Jenkins CI for more coverage.
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/75841/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark-ubuntu2404-intel-64,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/
@richardlau
richardlau
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
Been talking to @miladfarca about this:
16:01:57 === mjsunit/maglev/regress-498816446-3 ===
16:01:57 --- stderr ---
16:01:57 V8 is running with experimental features enabled. Stability and security will suffer.
16:01:57 --- stdout ---
16:01:57 test/mjsunit/maglev/regress-498816446-3.js:25: RangeError: Array buffer allocation failed
16:01:57 ta = new Int32Array(0xffffffff+1);
16:01:57 ^
16:01:57 RangeError: Array buffer allocation failed
16:01:57 at new ArrayBuffer (<anonymous>)
16:01:57 at new Int32Array (<anonymous>)
16:01:57 at test/mjsunit/maglev/regress-498816446-3.js:25:6
16:01:57 Command: out.gn/s390x.release/d8 --test test/mjsunit/mjsunit.js test/mjsunit/maglev/regress-498816446-3.js --random-seed=-770474680 --nohard-abort --allow-natives-syntax --maglev-object-tracking --maglev
16:01:57 16:01:57 ===
16:01:57 === 1 tests failed
16:01:57 ===
16:01:57 >>> 17287 base tests produced 15072 (87%) non-filtered tests
16:01:57 >>> 15072 tests ran

The Linux ppc64le and s390x machines being tested on have 8GB RAM and this test is allocating 16GB.
@miladfarca
miladfarca
commented
Aug 14, 2026

Copy link


Copy Markdown

Contributor
Patched it here: https://crrev.com/c/8252113

This was referenced Aug 18, 2026
 Open

 Merged

@joyeecheung
joyeecheung
commented
Aug 19, 2026

Copy link


Copy Markdown

Member
For the SEA test failures: they should not have run in the first place. #63751 should fix it.
@joyeecheung
joyeecheung
commented
Aug 20, 2026

Copy link


Copy Markdown

Member
This should fix the alpine failures https://chromium-review.googlesource.com/c/v8/v8/+/8254825
@sxasxa
mentioned this pull request
Aug 20, 2026

Open

hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 20, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[platform][posix] Fallback to conservative stack limit on musl
ba4ef8d
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs/node#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
joyeecheung added a commit
to targos/node
that referenced
this pull request
Aug 21, 2026
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
2163263
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
joyeecheungand others
added 17 commits
September 2, 2026 00:17
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
d17d73c
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@targos@joyeecheung
tools: update V8 gypfiles for 14.8
f819b6e
Co-Authored-By: Joyee Cheung <joyeec9h3@gmail.com>
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 14.9
71bee9e
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.0
0f22a95
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.1
20288e7
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
build: disable v8_postmortem_support
cc10b48
Post-mortem libraries should use v8's debug_helper library instead.
@targos@joyeecheung
src: migrate from deprecated xxxV2 APIs
e0c1284
- Set/GetPrototype
- Holder
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
src: migrate from v8::PropertyCallbackInfo<void>
54647f9
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
test: update wpt Wasm jsapi expectations
5431e04
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
test: update test-heapdump-vm-script.js for new version of V8
0376950
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
build: use ICU_UTIL_DATA_STATIC across V8
10b196c
ICU_UTIL_DATA_SHARED had been removed since
https://crrev.com/c/1513615, but Node.js still defined
it and relied on the removed path on Windows, so the ICU
initialization in mksnapshot had been silently failing
since then. https://crrev.com/c/7679153 made the failure
visible so the build started breaking on Windows. Fix it
by always using ICU_UTIL_DATA_STATIC since we already compile
the ICU data statically in.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
src: fix external reference registration for new CFunction lifetime
ac31ae3
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
test: update for new V8 serialization format
a45b843
V8 bumped its wire-format version from 0x0f to 0x10. Update the
expected hex in test-v8-serdes, and derive the v8 header bytes
dynamically in test-runner-v8-deserializer so it tracks future
bumps automatically.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@targos@joyeecheung
test: avoid worker in shared value conveyor test
f554209
V8 no longer supports JSON.parse on worker isolates while the shared
string table is enabled. Since --harmony-struct enables that table and
Node workers parse process.config during bootstrap,
use direct MessageChannel instead of a worker.
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@legendecas@joyeecheung
build: fix cppgc_base perfetto source scraper
e33a7c1
Signed-off-by: Chengzhong Wu <cwu631@bloomberg.net>
@joyeecheung
deps: V8: cherry-pick ba4ef8d72cde
7541bc4
Original commit message:
[platform][posix] Fallback to conservative stack limit on musl
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
Refs: v8/v8@ba4ef8d
@miladfarca@joyeecheung
deps: V8: cherry-pick 811fe8b04203
cd337e7
Original commit message:
Skip regress-498816446-3 when there is not enough memory
Currently causing a test failure on a machine with 8Gb of memory:
```
regress-498816446-3.js:25: RangeError: Array buffer allocation failed
```
Change-Id: I9e0396445c0b870d0070d666f9d6081b93e80f9c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8252113
Commit-Queue: Milad Farazmand <mfarazma@ibm.com>
Reviewed-by: Darius Mercadier <dmercadier@chromium.org>
Cr-Commit-Position: refs/heads/main@{#109426}
Refs: v8/v8@811fe8b
@StefanStojanovic@joyeecheung
build,win: fix
5f18227
Signed-off-by: StefanStojanovic <stefan.stojanovic@janeasystems.com>
@nodejs-github-bot
nodejs-github-bot
commented
Sep 1, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76860/
@aduh95
aduh95
commented
Sep 2, 2026

Copy link


Copy Markdown

Contributor
Test failing across multiple platforms:
---
duration_ms: 526.097
exitcode: 1
severity: fail
stack: |-
node:internal/assert/utils:146
throw error;
^
AssertionError [ERR_ASSERTION]: The input did not match the regular expression /kMaxReasonableBytes/. Input:
''
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-external-memory-reasonable-size.js:32:10)
at Module._compile (node:internal/modules/cjs/loader:1956:14)
at Object..js (node:internal/modules/cjs/loader:2096:10)
at Module.load (node:internal/modules/cjs/loader:1678:32)
at Module._load (node:internal/modules/cjs/loader:1470:12)
at wrapModuleLoad (node:internal/modules/cjs/loader:261:19)
at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
at node:internal/main/run_main_module:33:47 {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: '',
expected: /kMaxReasonableBytes/,
operator: 'match',
diff: 'simple'
}
Node.js v27.0.0-pre

@targos
targos
commented
Sep 2, 2026

Copy link


Copy Markdown

MemberAuthor
Just recompiled the branch. On my computer (macOS) it no longer prints the error and stack trace there's just:
➤ out/Debug/node --external-memory-max-reasonable-size=1 -e "new Float64Array(150_000_000)"
fish: Job 1, 'out/Debug/node --external-memor…' terminated by signal SIGTRAP (Trace or breakpoint trap)

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like a regression from #65589
@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like it's caused by https://chromium-review.googlesource.com/c/v8/v8/+/7705483, we should configure V8_LOGGING_LEVEL in gyp so that it prints something when CHECK fails.
@joyeecheung
build: derive V8_LOGGING_LEVEL from dcheck_always_on
5040994
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheungjoyeecheung
mentioned this pull request
Sep 2, 2026
 Open

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Pushed #65744 to this branch to check how the CI responds..
@nodejs-github-bot
nodejs-github-bot
commented
Sep 2, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76882/
@Renegade334Renegade334
mentioned this pull request
Sep 2, 2026
 Open

@eliau2005eliau2005
mentioned this pull request
Sep 3, 2026

Open

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

buildIssues and PRs related to Node.js builds or CI infrastructure.dependenciesPRs that add, update, or configure Node.js dependencies.needs-ciPRs that need a full CI run.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

10 participants

@targos@nodejs-github-bot@joyeecheung@richardlau@legendecas@miladfarca@StefanStojanovic@danmcd@aduh95@abmusse

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
deps: update V8 to 15.2 - #65161
Open
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Open
deps: update V8 to 15.2#65161
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Conversation
@targos
@targostargos
commented
Aug 9, 2026

Copy link


Copy Markdown

Member
Refs: #64784
@nodejs-github-bot
nodejs-github-bot
commented
Aug 9, 2026•

edited by targos

Loading

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/gyp
  •  @nodejs/security-wg
  •  @nodejs/v8
@targostargos
changed the title
deps: update V8 to 15.2.124.7deps: update V8 to 15.2Aug 9, 2026
@nodejs-github-botnodejs-github-bot
added

build
Issues and PRs related to Node.js builds or CI infrastructure.
dependencies
PRs that add, update, or configure Node.js dependencies.
needs-ci
PRs that need a full CI run.
labels
Aug 9, 2026
@targostargos
mentioned this pull request
Aug 9, 2026
 Open

@targos
targos
commented
Aug 9, 2026

Copy link


Copy Markdown

MemberAuthor
I guess this is blocked by #64408 (https://github.com/nodejs/node/actions/runs/31307061482/job/93228984418?pr=65161)
@joyeecheung
joyeecheung
commented
Aug 10, 2026

Copy link


Copy Markdown

Member
Uploaded https://chromium-review.googlesource.com/c/v8/v8/+/8223266 to fix the Linux AArch64 build (haven't tested on real Linux AArch64 yet, but that's what the error message suggests)
hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 13, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[simd] Disable SVE implementation of array search for GCC
68cf9ec
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs/node#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
targos pushed a commit
to targos/node
that referenced
this pull request
Aug 13, 2026
@joyeecheung@targos
deps: V8: cherry-pick 68cf9ecd884b
d356533
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@richardlau
richardlau
commented
Aug 13, 2026

Copy link


Copy Markdown

Member
FWIW https://chromium-review.googlesource.com/c/v8/v8/+/8236132 was opened by @sravani1510 to address the AIX build failure that is occurring on our V8 nightly builds.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@nodejs/platform-windows We're hitting a weird error on Windows:
https://github.com/nodejs/node/actions/runs/31699320590/job/94444346312?pr=65161
 Unexpected command-line argument "src/debug/debug-wasm-obects.q", expected a .tq file.
C:\Program Files\Microsoft Visual Studio\18\Enterprise\MSBuild\Microsoft\VC\v180\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for '..\..\out\Release\\torque.exe' exited with code 3. [D:\a\node\node\tools\v8_gypfiles\run_torque.vcxproj]

This wrong path doesn't exist in the code.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@legendecas Can you help with the perfetto build?
@legendecas
legendecas
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
Fixed the perfetto build. But I think the CI is failing for tests in large pages. Likely not related.
@targos
targos
commented
Aug 14, 2026

Copy link


Copy Markdown

MemberAuthor
Thanks. Summary of the remaining issues in GitHub CI:
I'll start a Jenkins CI for more coverage.
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/75841/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark-ubuntu2404-intel-64,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/
@richardlau
richardlau
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
Been talking to @miladfarca about this:
16:01:57 === mjsunit/maglev/regress-498816446-3 ===
16:01:57 --- stderr ---
16:01:57 V8 is running with experimental features enabled. Stability and security will suffer.
16:01:57 --- stdout ---
16:01:57 test/mjsunit/maglev/regress-498816446-3.js:25: RangeError: Array buffer allocation failed
16:01:57 ta = new Int32Array(0xffffffff+1);
16:01:57 ^
16:01:57 RangeError: Array buffer allocation failed
16:01:57 at new ArrayBuffer (<anonymous>)
16:01:57 at new Int32Array (<anonymous>)
16:01:57 at test/mjsunit/maglev/regress-498816446-3.js:25:6
16:01:57 Command: out.gn/s390x.release/d8 --test test/mjsunit/mjsunit.js test/mjsunit/maglev/regress-498816446-3.js --random-seed=-770474680 --nohard-abort --allow-natives-syntax --maglev-object-tracking --maglev
16:01:57 16:01:57 ===
16:01:57 === 1 tests failed
16:01:57 ===
16:01:57 >>> 17287 base tests produced 15072 (87%) non-filtered tests
16:01:57 >>> 15072 tests ran

The Linux ppc64le and s390x machines being tested on have 8GB RAM and this test is allocating 16GB.
@miladfarca
miladfarca
commented
Aug 14, 2026

Copy link


Copy Markdown

Contributor
Patched it here: https://crrev.com/c/8252113

This was referenced Aug 18, 2026
 Open

 Merged

@joyeecheung
joyeecheung
commented
Aug 19, 2026

Copy link


Copy Markdown

Member
For the SEA test failures: they should not have run in the first place. #63751 should fix it.
@joyeecheung
joyeecheung
commented
Aug 20, 2026

Copy link


Copy Markdown

Member
This should fix the alpine failures https://chromium-review.googlesource.com/c/v8/v8/+/8254825
@sxasxa
mentioned this pull request
Aug 20, 2026

Open

hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 20, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[platform][posix] Fallback to conservative stack limit on musl
ba4ef8d
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs/node#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
joyeecheung added a commit
to targos/node
that referenced
this pull request
Aug 21, 2026
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
2163263
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
joyeecheungand others
added 17 commits
September 2, 2026 00:17
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
d17d73c
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@targos@joyeecheung
tools: update V8 gypfiles for 14.8
f819b6e
Co-Authored-By: Joyee Cheung <joyeec9h3@gmail.com>
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 14.9
71bee9e
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.0
0f22a95
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.1
20288e7
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
build: disable v8_postmortem_support
cc10b48
Post-mortem libraries should use v8's debug_helper library instead.
@targos@joyeecheung
src: migrate from deprecated xxxV2 APIs
e0c1284
- Set/GetPrototype
- Holder
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
src: migrate from v8::PropertyCallbackInfo<void>
54647f9
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
test: update wpt Wasm jsapi expectations
5431e04
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
test: update test-heapdump-vm-script.js for new version of V8
0376950
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
build: use ICU_UTIL_DATA_STATIC across V8
10b196c
ICU_UTIL_DATA_SHARED had been removed since
https://crrev.com/c/1513615, but Node.js still defined
it and relied on the removed path on Windows, so the ICU
initialization in mksnapshot had been silently failing
since then. https://crrev.com/c/7679153 made the failure
visible so the build started breaking on Windows. Fix it
by always using ICU_UTIL_DATA_STATIC since we already compile
the ICU data statically in.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
src: fix external reference registration for new CFunction lifetime
ac31ae3
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
test: update for new V8 serialization format
a45b843
V8 bumped its wire-format version from 0x0f to 0x10. Update the
expected hex in test-v8-serdes, and derive the v8 header bytes
dynamically in test-runner-v8-deserializer so it tracks future
bumps automatically.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@targos@joyeecheung
test: avoid worker in shared value conveyor test
f554209
V8 no longer supports JSON.parse on worker isolates while the shared
string table is enabled. Since --harmony-struct enables that table and
Node workers parse process.config during bootstrap,
use direct MessageChannel instead of a worker.
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@legendecas@joyeecheung
build: fix cppgc_base perfetto source scraper
e33a7c1
Signed-off-by: Chengzhong Wu <cwu631@bloomberg.net>
@joyeecheung
deps: V8: cherry-pick ba4ef8d72cde
7541bc4
Original commit message:
[platform][posix] Fallback to conservative stack limit on musl
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
Refs: v8/v8@ba4ef8d
@miladfarca@joyeecheung
deps: V8: cherry-pick 811fe8b04203
cd337e7
Original commit message:
Skip regress-498816446-3 when there is not enough memory
Currently causing a test failure on a machine with 8Gb of memory:
```
regress-498816446-3.js:25: RangeError: Array buffer allocation failed
```
Change-Id: I9e0396445c0b870d0070d666f9d6081b93e80f9c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8252113
Commit-Queue: Milad Farazmand <mfarazma@ibm.com>
Reviewed-by: Darius Mercadier <dmercadier@chromium.org>
Cr-Commit-Position: refs/heads/main@{#109426}
Refs: v8/v8@811fe8b
@StefanStojanovic@joyeecheung
build,win: fix
5f18227
Signed-off-by: StefanStojanovic <stefan.stojanovic@janeasystems.com>
@nodejs-github-bot
nodejs-github-bot
commented
Sep 1, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76860/
@aduh95
aduh95
commented
Sep 2, 2026

Copy link


Copy Markdown

Contributor
Test failing across multiple platforms:
---
duration_ms: 526.097
exitcode: 1
severity: fail
stack: |-
node:internal/assert/utils:146
throw error;
^
AssertionError [ERR_ASSERTION]: The input did not match the regular expression /kMaxReasonableBytes/. Input:
''
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-external-memory-reasonable-size.js:32:10)
at Module._compile (node:internal/modules/cjs/loader:1956:14)
at Object..js (node:internal/modules/cjs/loader:2096:10)
at Module.load (node:internal/modules/cjs/loader:1678:32)
at Module._load (node:internal/modules/cjs/loader:1470:12)
at wrapModuleLoad (node:internal/modules/cjs/loader:261:19)
at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
at node:internal/main/run_main_module:33:47 {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: '',
expected: /kMaxReasonableBytes/,
operator: 'match',
diff: 'simple'
}
Node.js v27.0.0-pre

@targos
targos
commented
Sep 2, 2026

Copy link


Copy Markdown

MemberAuthor
Just recompiled the branch. On my computer (macOS) it no longer prints the error and stack trace there's just:
➤ out/Debug/node --external-memory-max-reasonable-size=1 -e "new Float64Array(150_000_000)"
fish: Job 1, 'out/Debug/node --external-memor…' terminated by signal SIGTRAP (Trace or breakpoint trap)

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like a regression from #65589
@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like it's caused by https://chromium-review.googlesource.com/c/v8/v8/+/7705483, we should configure V8_LOGGING_LEVEL in gyp so that it prints something when CHECK fails.
@joyeecheung
build: derive V8_LOGGING_LEVEL from dcheck_always_on
5040994
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheungjoyeecheung
mentioned this pull request
Sep 2, 2026
 Open

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Pushed #65744 to this branch to check how the CI responds..
@nodejs-github-bot
nodejs-github-bot
commented
Sep 2, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76882/
@Renegade334Renegade334
mentioned this pull request
Sep 2, 2026
 Open

@eliau2005eliau2005
mentioned this pull request
Sep 3, 2026

Open

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

buildIssues and PRs related to Node.js builds or CI infrastructure.dependenciesPRs that add, update, or configure Node.js dependencies.needs-ciPRs that need a full CI run.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

10 participants

@targos@nodejs-github-bot@joyeecheung@richardlau@legendecas@miladfarca@StefanStojanovic@danmcd@aduh95@abmusse

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
deps: update V8 to 15.2 - #65161
Open
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Open
deps: update V8 to 15.2#65161
targos wants to merge 31 commits into
nodejs:mainfrom 
targos:v8-152
Conversation
@targos
@targostargos
commented
Aug 9, 2026

Copy link


Copy Markdown

Member
Refs: #64784
@nodejs-github-bot
nodejs-github-bot
commented
Aug 9, 2026•

edited by targos

Loading

Copy link


Copy Markdown

Collaborator
Review requested:
  •  @nodejs/gyp
  •  @nodejs/security-wg
  •  @nodejs/v8
@targostargos
changed the title
deps: update V8 to 15.2.124.7deps: update V8 to 15.2Aug 9, 2026
@nodejs-github-botnodejs-github-bot
added

build
Issues and PRs related to Node.js builds or CI infrastructure.
dependencies
PRs that add, update, or configure Node.js dependencies.
needs-ci
PRs that need a full CI run.
labels
Aug 9, 2026
@targostargos
mentioned this pull request
Aug 9, 2026
 Open

@targos
targos
commented
Aug 9, 2026

Copy link


Copy Markdown

MemberAuthor
I guess this is blocked by #64408 (https://github.com/nodejs/node/actions/runs/31307061482/job/93228984418?pr=65161)
@joyeecheung
joyeecheung
commented
Aug 10, 2026

Copy link


Copy Markdown

Member
Uploaded https://chromium-review.googlesource.com/c/v8/v8/+/8223266 to fix the Linux AArch64 build (haven't tested on real Linux AArch64 yet, but that's what the error message suggests)
hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 13, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[simd] Disable SVE implementation of array search for GCC
68cf9ec
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs/node#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
targos pushed a commit
to targos/node
that referenced
this pull request
Aug 13, 2026
@joyeecheung@targos
deps: V8: cherry-pick 68cf9ecd884b
d356533
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@richardlau
richardlau
commented
Aug 13, 2026

Copy link


Copy Markdown

Member
FWIW https://chromium-review.googlesource.com/c/v8/v8/+/8236132 was opened by @sravani1510 to address the AIX build failure that is occurring on our V8 nightly builds.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@nodejs/platform-windows We're hitting a weird error on Windows:
https://github.com/nodejs/node/actions/runs/31699320590/job/94444346312?pr=65161
 Unexpected command-line argument "src/debug/debug-wasm-obects.q", expected a .tq file.
C:\Program Files\Microsoft Visual Studio\18\Enterprise\MSBuild\Microsoft\VC\v180\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for '..\..\out\Release\\torque.exe' exited with code 3. [D:\a\node\node\tools\v8_gypfiles\run_torque.vcxproj]

This wrong path doesn't exist in the code.
@targos
targos
commented
Aug 13, 2026

Copy link


Copy Markdown

MemberAuthor
@legendecas Can you help with the perfetto build?
@legendecas
legendecas
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
Fixed the perfetto build. But I think the CI is failing for tests in large pages. Likely not related.
@targos
targos
commented
Aug 14, 2026

Copy link


Copy Markdown

MemberAuthor
Thanks. Summary of the remaining issues in GitHub CI:
I'll start a Jenkins CI for more coverage.
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/75841/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark-ubuntu2404-intel-64,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
@nodejs-github-bot
nodejs-github-bot
commented
Aug 14, 2026

Copy link


Copy Markdown

Collaborator
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/
@richardlau
richardlau
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/7311/

V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-power9le,v8test=v8test/7311/
Been talking to @miladfarca about this:
16:01:57 === mjsunit/maglev/regress-498816446-3 ===
16:01:57 --- stderr ---
16:01:57 V8 is running with experimental features enabled. Stability and security will suffer.
16:01:57 --- stdout ---
16:01:57 test/mjsunit/maglev/regress-498816446-3.js:25: RangeError: Array buffer allocation failed
16:01:57 ta = new Int32Array(0xffffffff+1);
16:01:57 ^
16:01:57 RangeError: Array buffer allocation failed
16:01:57 at new ArrayBuffer (<anonymous>)
16:01:57 at new Int32Array (<anonymous>)
16:01:57 at test/mjsunit/maglev/regress-498816446-3.js:25:6
16:01:57 Command: out.gn/s390x.release/d8 --test test/mjsunit/mjsunit.js test/mjsunit/maglev/regress-498816446-3.js --random-seed=-770474680 --nohard-abort --allow-natives-syntax --maglev-object-tracking --maglev
16:01:57 16:01:57 ===
16:01:57 === 1 tests failed
16:01:57 ===
16:01:57 >>> 17287 base tests produced 15072 (87%) non-filtered tests
16:01:57 >>> 15072 tests ran

The Linux ppc64le and s390x machines being tested on have 8GB RAM and this test is allocating 16GB.
@miladfarca
miladfarca
commented
Aug 14, 2026

Copy link


Copy Markdown

Contributor
Patched it here: https://crrev.com/c/8252113

This was referenced Aug 18, 2026
 Open

 Merged

@joyeecheung
joyeecheung
commented
Aug 19, 2026

Copy link


Copy Markdown

Member
For the SEA test failures: they should not have run in the first place. #63751 should fix it.
@joyeecheung
joyeecheung
commented
Aug 20, 2026

Copy link


Copy Markdown

Member
This should fix the alpine failures https://chromium-review.googlesource.com/c/v8/v8/+/8254825
@sxasxa
mentioned this pull request
Aug 20, 2026

Open

hubot pushed a commit
to v8/v8
that referenced
this pull request
Aug 20, 2026
@joyeecheungv8-scoped@luci-project-accounts.iam.gserviceaccount.com
[platform][posix] Fallback to conservative stack limit on musl
ba4ef8d
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs/node#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
joyeecheung added a commit
to targos/node
that referenced
this pull request
Aug 21, 2026
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
2163263
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
joyeecheungand others
added 17 commits
September 2, 2026 00:17
@joyeecheung
deps: V8: cherry-pick 68cf9ecd884b
d17d73c
Original commit message:
[simd] Disable SVE implementation of array search for GCC
GCC requires SVE enabled for the entire translation unit and does
not expose raw __builtin_sve_* builtins on a per-function basis.
Fallback to Neon if it's not built by Clang.
Refs: nodejs#65161
Change-Id: I53a06fcf8f901ae0347044c6999463ce99215c45
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8223266
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109230}
Refs: v8/v8@68cf9ec
@targos@joyeecheung
tools: update V8 gypfiles for 14.8
f819b6e
Co-Authored-By: Joyee Cheung <joyeec9h3@gmail.com>
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 14.9
71bee9e
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.0
0f22a95
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
tools: update V8 gypfiles for 15.1
20288e7
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
build: disable v8_postmortem_support
cc10b48
Post-mortem libraries should use v8's debug_helper library instead.
@targos@joyeecheung
src: migrate from deprecated xxxV2 APIs
e0c1284
- Set/GetPrototype
- Holder
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
src: migrate from v8::PropertyCallbackInfo<void>
54647f9
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@targos@joyeecheung
test: update wpt Wasm jsapi expectations
5431e04
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@joyeecheung
test: update test-heapdump-vm-script.js for new version of V8
0376950
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
build: use ICU_UTIL_DATA_STATIC across V8
10b196c
ICU_UTIL_DATA_SHARED had been removed since
https://crrev.com/c/1513615, but Node.js still defined
it and relied on the removed path on Windows, so the ICU
initialization in mksnapshot had been silently failing
since then. https://crrev.com/c/7679153 made the failure
visible so the build started breaking on Windows. Fix it
by always using ICU_UTIL_DATA_STATIC since we already compile
the ICU data statically in.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
src: fix external reference registration for new CFunction lifetime
ac31ae3
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheung
test: update for new V8 serialization format
a45b843
V8 bumped its wire-format version from 0x0f to 0x10. Update the
expected hex in test-v8-serdes, and derive the v8 header bytes
dynamically in test-runner-v8-deserializer so it tracks future
bumps automatically.
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@targos@joyeecheung
test: avoid worker in shared value conveyor test
f554209
V8 no longer supports JSON.parse on worker isolates while the shared
string table is enabled. Since --harmony-struct enables that table and
Node workers parse process.config during bootstrap,
use direct MessageChannel instead of a worker.
Signed-Off-By: Michaël Zasso <targos@protonmail.com>
@legendecas@joyeecheung
build: fix cppgc_base perfetto source scraper
e33a7c1
Signed-off-by: Chengzhong Wu <cwu631@bloomberg.net>
@joyeecheung
deps: V8: cherry-pick ba4ef8d72cde
7541bc4
Original commit message:
[platform][posix] Fallback to conservative stack limit on musl
For most libcs, pthread_getattr_np() returns the the stack reserved
limit on the main thread, but musl only returns the current high-water
mark at the time of the call. There's no macro to detect musl, so just
fallback to the conservative stack limit in cases where the libc is
not one that is known to work.
Refs: nodejs#65161
Change-Id: Ie2b51269b9e8d2d3451d5d68ad1a233d396af935
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8254825
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Joyee Cheung <joyee@igalia.com>
Cr-Commit-Position: refs/heads/main@{#109406}
Refs: v8/v8@ba4ef8d
@miladfarca@joyeecheung
deps: V8: cherry-pick 811fe8b04203
cd337e7
Original commit message:
Skip regress-498816446-3 when there is not enough memory
Currently causing a test failure on a machine with 8Gb of memory:
```
regress-498816446-3.js:25: RangeError: Array buffer allocation failed
```
Change-Id: I9e0396445c0b870d0070d666f9d6081b93e80f9c
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8252113
Commit-Queue: Milad Farazmand <mfarazma@ibm.com>
Reviewed-by: Darius Mercadier <dmercadier@chromium.org>
Cr-Commit-Position: refs/heads/main@{#109426}
Refs: v8/v8@811fe8b
@StefanStojanovic@joyeecheung
build,win: fix
5f18227
Signed-off-by: StefanStojanovic <stefan.stojanovic@janeasystems.com>
@nodejs-github-bot
nodejs-github-bot
commented
Sep 1, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76860/
@aduh95
aduh95
commented
Sep 2, 2026

Copy link


Copy Markdown

Contributor
Test failing across multiple platforms:
---
duration_ms: 526.097
exitcode: 1
severity: fail
stack: |-
node:internal/assert/utils:146
throw error;
^
AssertionError [ERR_ASSERTION]: The input did not match the regular expression /kMaxReasonableBytes/. Input:
''
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-external-memory-reasonable-size.js:32:10)
at Module._compile (node:internal/modules/cjs/loader:1956:14)
at Object..js (node:internal/modules/cjs/loader:2096:10)
at Module.load (node:internal/modules/cjs/loader:1678:32)
at Module._load (node:internal/modules/cjs/loader:1470:12)
at wrapModuleLoad (node:internal/modules/cjs/loader:261:19)
at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
at node:internal/main/run_main_module:33:47 {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: '',
expected: /kMaxReasonableBytes/,
operator: 'match',
diff: 'simple'
}
Node.js v27.0.0-pre

@targos
targos
commented
Sep 2, 2026

Copy link


Copy Markdown

MemberAuthor
Just recompiled the branch. On my computer (macOS) it no longer prints the error and stack trace there's just:
➤ out/Debug/node --external-memory-max-reasonable-size=1 -e "new Float64Array(150_000_000)"
fish: Job 1, 'out/Debug/node --external-memor…' terminated by signal SIGTRAP (Trace or breakpoint trap)

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like a regression from #65589
@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Looks like it's caused by https://chromium-review.googlesource.com/c/v8/v8/+/7705483, we should configure V8_LOGGING_LEVEL in gyp so that it prints something when CHECK fails.
@joyeecheung
build: derive V8_LOGGING_LEVEL from dcheck_always_on
5040994
Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
@joyeecheungjoyeecheung
mentioned this pull request
Sep 2, 2026
 Open

@joyeecheung
joyeecheung
commented
Sep 2, 2026

Copy link


Copy Markdown

Member
Pushed #65744 to this branch to check how the CI responds..
@nodejs-github-bot
nodejs-github-bot
commented
Sep 2, 2026

Copy link


Copy Markdown

Collaborator
CI: https://ci.nodejs.org/job/node-test-pull-request/76882/
@Renegade334Renegade334
mentioned this pull request
Sep 2, 2026
 Open

@eliau2005eliau2005
mentioned this pull request
Sep 3, 2026

Open

Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

buildIssues and PRs related to Node.js builds or CI infrastructure.dependenciesPRs that add, update, or configure Node.js dependencies.needs-ciPRs that need a full CI run.

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

10 participants

@targos@nodejs-github-bot@joyeecheung@richardlau@legendecas@miladfarca@StefanStojanovic@danmcd@aduh95@abmusse