GeezerVison is showing github.com — deps: update V8 to 12.2 by targos · Pull Request #51362 · nodejs/node
Conversation
targos
commented
Jan 4, 2024
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
Main change that affects us: v8/v8@12203e0
Some flaky tests.
I would really appreciate help to investigate these. Node.js 22 is coming close!
12:33:52 not ok 3759 parallel/test-worker-arraybuffer-zerofill
12:33:52 ---
12:33:52 duration_ms: 120024.23700
12:33:52 severity: fail
12:33:52 exitcode: -15
12:33:52 stack: |-
12:33:52 timeout
12:33:52 ...
12:40:34 not ok 3756 parallel/test-net-write-fully-async-hex-string
12:40:34 ---
12:40:34 duration_ms: 120066.81500
12:40:34 severity: fail
12:40:34 exitcode: -15
12:40:34 stack: |-
12:40:34 timeout
12:40:34 ...
18:25:43 not ok 2444 parallel/test-shadow-realm-gc-module
18:25:43 ---
18:25:43 duration_ms: 6465.44100
18:25:43 severity: crashed
18:25:43 exitcode: -6
18:25:43 stack: |-
18:25:43
18:25:43 <--- Last few GCs --->
18:25:43 .6[1674180:0x7f32cac7f000] 5861 ms: Mark-Compact 18.1 (48.4) -> 15.5 (49.2) MB, pooled: 0 MB, 5.89 / 0.01 ms (+ 16.5 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 26 ms) (average mu = 0.722, current mu = 0.7[1674180:0x7f32cac7f000] 6033 ms: Mark-Compact 22.4 (50.2) -> 18.8 (52.7) MB, pooled: 0 MB, 33.08 / 0.01 ms (+ 29.2 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 134 ms) (average mu = 0.666, current mu = 0
18:25:43
18:25:43 <--- JS stacktrace --->
18:25:43
18:25:43 FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
18:25:43 ----- Native stack trace -----
18:25:43
18:25:43 ...
18:46:01 not ok 2691 parallel/test-shadow-realm-gc
18:46:01 ---
18:46:01 duration_ms: 3138.09900
18:46:01 severity: crashed
18:46:01 exitcode: -11
18:46:01 stack: |-
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
bricss, BlackIQ, abhaysinghs772, PPROGER, hunghg255, iamthepoe, tungbq, joansebgarcia, gcaaa31928, hausg, and 153 more reacted with thumbs up emoji
yanickouellette1982, Dmitriy-Frostoff, mozhuanzuojing, akshitagupta15june, and ssi02014 reacted with laugh emoji
bricss, lin72h, ad0x99, DaanQ42, damnitrahul, denisapelnikov, danielgospodinow, aadito123, deki23, marco-ippolito, and 17 more reacted with hooray emoji
bricss, filipecorrea, lucasrivoiro, Kuuuuuuuu, rumon5h, kyotrandev, siddharthsabron, damnitrahul, wakidurrahman, denisapelnikov, and 22 more reacted with heart emoji
bricss, CogitoBurrito, dtmrc, DaanQ42, damnitrahul, BreadGenie, tryb3l, denisapelnikov, j1m-ryan, lin72h, and 24 more reacted with rocket emoji
yvele, damnitrahul, akshitagupta15june, bricss, siosio34, marco-ippolito, guojingkang, parasatiskylar, Dmitriy-Frostoff, ChrisChou-freeman, and 5 more reacted with eyes emoji
All reactions
-
👍
163 reactions
-
😄
5 reactions
-
🎉
27 reactions
-
❤️
32 reactions
-
🚀
34 reactions
-
👀
15 reactions
targos
added
help wanted
Issues that need assistance from volunteers or PRs that need help to proceed.
semver-major
PRs that contain breaking changes and should be released in the next major version.
v8 engine
Issues and PRs related to the V8 dependency.
labels
Jan 4, 2024
|
Review requested:
- @nodejs/gyp
- @nodejs/v8-update
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This was referenced Jan 7, 2024
targos
added
the
request-ci
Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review.
label
Jan 7, 2024
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
It looks like 9570832 is not enough. There's a flaky test in debug mode:
./node_g test/sequential/test-worker-fshandles-error-on-termination.js
$ ./node_g test/sequential/test-worker-fshandles-error-on-termination.js
#
# Fatal error in ../../deps/v8/src/execution/isolate-inl.h, line 105
# Debug check failed: has_exception() == result == ReadOnlyRoots(this).exception() (1 vs. 0).
#
#
#
#FailureMessage Object: 0x16f6ed148
----- Native stack trace -----
1: 0x1048b5400 node::DumpNativeBacktrace(__sFILE*) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
2: 0x104afddd4 node::NodePlatform::GetStackTracePrinter()::$_3::operator()() const [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
3: 0x104afdd90 node::NodePlatform::GetStackTracePrinter()::$_3::__invoke() [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
4: 0x106c702f0 V8_Fatal(char const*, int, char const*, ...) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
5: 0x106c6fe8c std::__1::enable_if<!std::is_function<std::__1::remove_pointer<char>::type>::value && !std::is_enum<char>::value && has_output_operator<char, v8::base::CheckMessageStream>::value, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>>>::type v8::base::PrintCheckOperand<char>(char) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
6: 0x104ebb208 v8::internal::Isolate::VerifyBuiltinsResult(v8::internal::Tagged<v8::internal::Object>) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
7: 0x105a4943c v8::internal::Runtime_PromiseRejectEventFromStack(int, unsigned long*, v8::internal::Isolate*) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
8: 0x10615e7b4 Builtins_CEntry_Return1_ArgvOnStack_NoBuiltinExit [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
9: 0x1061edabc Builtins_PromiseReject [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
10: 0x1060bc370 Builtins_InterpreterEntryTrampoline [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
11: 0x1061f9420 Builtins_PromiseRejectReactionJob [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
12: 0x1060eb2ec Builtins_RunMicrotasks [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
13: 0x1060b96f4 Builtins_JSRunMicrotasksEntry [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
14: 0x105131e9c v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate*, v8::internal::(anonymous namespace)::InvokeParams const&) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
15: 0x105133870 v8::internal::(anonymous namespace)::InvokeWithTryCatch(v8::internal::Isolate*, v8::internal::(anonymous namespace)::InvokeParams const&) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
16: 0x105133f20 v8::internal::Execution::TryRunMicrotasks(v8::internal::Isolate*, v8::internal::MicrotaskQueue*) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
17: 0x105186dec v8::internal::MicrotaskQueue::RunMicrotasks(v8::internal::Isolate*) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
18: 0x105186b0c v8::internal::MicrotaskQueue::PerformCheckpointInternal(v8::Isolate*) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
19: 0x1047f7110 node::InternalCallbackScope::Close() [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
20: 0x1047f6f2c node::InternalCallbackScope::~InternalCallbackScope() [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
21: 0x1047f6a3c node::InternalCallbackScope::~InternalCallbackScope() [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
22: 0x1049ec984 node::fs::FSReqPromise<node::AliasedBufferBase<double, v8::Float64Array>>::Reject(v8::Local<v8::Value>) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
23: 0x104a061fc node::fs::FSReqAfterScope::Reject(uv_fs_s*) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
24: 0x104a06324 node::fs::FSReqAfterScope::Proceed() [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
25: 0x104a06be0 node::fs::AfterOpenFileHandle(uv_fs_s*) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
26: 0x1049ee5bc node::MakeLibuvRequestCallback<uv_fs_s, void (*)(uv_fs_s*)>::Wrapper(uv_fs_s*) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
27: 0x10608c3c4 uv__fs_done [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
28: 0x10607e4ec uv__work_done [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
29: 0x1060874d0 uv__async_io [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
30: 0x1060aaea0 uv__io_poll [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
31: 0x106087ed0 uv_run [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
32: 0x1047fa37c node::SpinEventLoopInternal(node::Environment*) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
33: 0x104ba3c34 node::worker::Worker::Run() [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
34: 0x104ba7cb8 node::worker::Worker::StartThread(v8::FunctionCallbackInfo<v8::Value> const&)::$_3::operator()(void*) const [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
35: 0x104ba7c64 node::worker::Worker::StartThread(v8::FunctionCallbackInfo<v8::Value> const&)::$_3::__invoke(void*) [/Users/mzasso/git/nodejs/v8-next-update/out/Debug/node]
36: 0x1843de034 _pthread_start [/usr/lib/system/libsystem_pthread.dylib]
37: 0x1843d8e3c thread_start [/usr/lib/system/libsystem_pthread.dylib]
[1] 34458 trace trap ./node_g test/sequential/test-worker-fshandles-error-on-termination.js
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
/cc @nodejs/platform-windows @StefanStojanovic We're hitting nodejs/node-v8#271
Thanks for letting me know. I just got back to work today, so will look into it in the following days.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
@sumitradawn This is not with V8 HEAD. It's with 12.1-lkgr
@targos I have tried to build Node from the source code on AIX and it is quite fine for me. There might be some memory issue, Can you please try to run the job with -j4 option.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Previous limit was too low for debug builds.
|
Rebased and added flaky designations to the tests.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
aduh95
left a comment
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for the hard work! Non-blocking comment: I wonder if d5ac47e and 59e4518 should be backported
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
targos
commented
Mar 31, 2024
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
sjrd and bricss reacted with hooray emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Reviewers
mcollina
mcollina approved these changes
aduh95
aduh95 approved these changes
Uh oh!
There was an error while loading. Please reload this page.
Labels
build
Issues and PRs related to Node.js builds or CI infrastructure.
needs-ci
PRs that need a full CI run.
semver-major
PRs that contain breaking changes and should be released in the next major version.
v8 engine
Issues and PRs related to the V8 dependency.
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|