You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
es-module/test-typescript timing out and failing on AIX on v25.x-staging #61017
$ git bisect log
git bisect start 'bad'
# status: waiting for both good and bad commits
# good: [fc996fd4da671792c13d016e9b1a7994d28b6f68] Working on v25.2.2
git bisect good fc996fd4da671792c13d016e9b1a7994d28b6f68
# status: waiting for bad commit, 1 good commit known
# bad: [eb0705a5c8ffdf268008d7b6435a0fd24cec2dbb] test: skip tests not passing without `NODE_OPTIONS` support
git bisect bad eb0705a5c8ffdf268008d7b6435a0fd24cec2dbb
# bad: [cb8d53bdb735181721c021a86a9207f779b310ef] deps: add temporal_rs 0.1.0
git bisect bad cb8d53bdb735181721c021a86a9207f779b310ef
# bad: [d9bc0bf4fbb9dad0ab4b51fa643cf264090a2d16] test: ensure assertions are reached on HTTP2 tests
git bisect bad d9bc0bf4fbb9dad0ab4b51fa643cf264090a2d16
# bad: [29d031831dc4fc2af700f90057f7afa8fcb5f4a1] meta: add Renegade334 to collaborators
git bisect bad 29d031831dc4fc2af700f90057f7afa8fcb5f4a1
# good: [4809273418e4adce06eb464ce9bb6d951df05fd5] benchmark: use typescript for import cjs benchmark
git bisect good 4809273418e4adce06eb464ce9bb6d951df05fd5
# bad: [4eeb0d105536c68f0af957baf7af714fca069fc2] test: fix test-buffer-zero-fill-cli to be effective
git bisect bad 4eeb0d105536c68f0af957baf7af714fca069fc2
# bad: [712f944bef3f88bca180c2cfdb7167fd5d4ca01b] doc: `domain.add()` does not accept timer objects
git bisect bad 712f944bef3f88bca180c2cfdb7167fd5d4ca01b
# bad: [bf27b859f2c7ab7c1f9faaf25e37c018f0ca97ac] esm: use wasm version of cjs-module-lexer
git bisect bad bf27b859f2c7ab7c1f9faaf25e37c018f0ca97ac
# first bad commit: [bf27b859f2c7ab7c1f9faaf25e37c018f0ca97ac] esm: use wasm version of cjs-module-lexer
$
bf27b85 is part of #60663. AFAIK we've not seen the es-module/test-typescript failures on main but they are persistent on v25.x-staging. Maybe due to the different version of V8?
It's unlikely that we'll have another v25.x release (and even more so that it would contain the offending commit, which doesn't fail on main so presumably wouldn't on v26.x).
Activity
richardlau commentedon Dec 10, 2025
Double check CI against
v25.x(fc996fd): https://ci.nodejs.org/job/node-test-commit-aix/60153/richardlau commentedon Dec 10, 2025
Passed. Bisecting.
cb8d53b https://ci.nodejs.org/job/node-test-commit-aix/60160/ failed
d9bc0bf https://ci.nodejs.org/job/node-test-commit-aix/60163/ failed
29d0318 https://ci.nodejs.org/job/node-test-commit-aix/60165/ failed
4809273 https://ci.nodejs.org/job/node-test-commit-aix/60166/ passed
4eeb0d1 https://ci.nodejs.org/job/node-test-commit-aix/60167/ failed
712f944 https://ci.nodejs.org/job/node-test-commit-aix/60170/ failed
bf27b85 https://ci.nodejs.org/job/node-test-commit-aix/60172/ failed
bf27b85 is part of #60663. AFAIK we've not seen the
es-module/test-typescriptfailures onmainbut they are persistent onv25.x-staging. Maybe due to the different version of V8?aduh95 commentedon Jan 10, 2026
Removing bf27b85 from staging did fix the AIX CI: https://ci.nodejs.org/job/node-test-commit/84731/
richardlau commentedon Apr 30, 2026
It's unlikely that we'll have another v25.x release (and even more so that it would contain the offending commit, which doesn't fail on main so presumably wouldn't on v26.x).