-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
src: move v8::HandleScope call to Emit #20045
Conversation
CI: https://ci.nodejs.org/job/node-test-commit/17773/ (Not sure if the benchmark CI works, had to specify |
@addaleax are you certain you ran the correct benchmarks? I think you wanted to run |
@BridgeAR Yeah, that benchmark run missed its target. Maybe I screwed up editing the HTML. Anyway, when trying to enter @nodejs/build Could you turn |
@addaleax would you like to try again with the benchmark CI? |
Rerunning normal CI. |
Remove redundant calls to v8::HandleScope in the contructor and destructor for the AsyncScope class Refs: nodejs#19972 (comment) Refs: nodejs#20045
I couldn't spot the failing test in https://ci.nodejs.org/job/node-test-commit-linux/18087/nodes=fedora-last-latest-x64/console |
Okay, we have |
Look in the full console log: |
|
Reran CI: https://ci.nodejs.org/job/node-test-pull-request/14370/ (To make sure it wasn't just a flaky test) |
Again, a total random failure: not ok 495 parallel/test-cluster-setup-master
---
duration_ms: 120.220
severity: fail
exitcode: -15
stack: |-
timeout
... Somebody help? |
Honestly, the osx log doesn't even specify what went wrong, I think (https://ci.nodejs.org/job/node-test-commit-osx/nodes=osx1010/17933/consoleFull) |
171f3d8
to
b9b7b01
Compare
Move v8::HandleScope call to Emit removing it from previous locations where it was added to avoid crashing (constructor and destructor of AsyncWrap) for a more general and fool-proof solution. Ref: nodejs#19972 (comment)
Restarting CI after rebasing on top of current master. |
Restarting after OSX was fixed in #20139. |
@Trott OSX passes for this one! 🎉 Another random failure? damn. BSD never failed on this one. Lemme rebuild. |
23:55:31 not ok 2150 sequential/test-debugger-debug-brk
23:55:31 ---
23:55:31 duration_ms: 0.540
23:55:31 severity: fail
23:55:31 exitcode: 1
23:55:31 stack: |-
23:55:31 assert.js:77
23:55:31 throw new AssertionError(obj);
23:55:31 ^
23:55:31
23:55:31 AssertionError [ERR_ASSERTION]: '/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/out/Release/node --inspect --debug-brk /usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/fixtures/empty.js' should not quit
23:55:31 at ChildProcess.fail (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/sequential/test-debugger-debug-brk.js:19:29)
23:55:31 at ChildProcess.emit (events.js:182:13)
23:55:31 at Process.ChildProcess._handle.onexit (internal/child_process.js:222:12) Completely unrelated, rebuilding. |
Re-running just FreeBSD: https://ci.nodejs.org/job/node-test-commit-freebsd/17164/ |
@Trott it passed! Should I make an issue for a flaky test? BTW, I'm landing this. It has been open for 5 days and has been approved by a ton of people. |
Landed in e32eddc |
Move v8::HandleScope call to Emit removing it from previous locations where it was added to avoid crashing (constructor and destructor of AsyncWrap) for a more general and fool-proof solution. Ref: #19972 (comment) PR-URL: #20045 Reviewed-By: Yang Guo <yangguo@chromium.org> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com>
If an issue doesn't exist, that would be helpful. We should always do that, but I know I don't because...so many flaky tests...only so many hours to spend in the Node.js issue tracker a day, you know? :-D In that particular case, flakiness might be because some other process is taking the predefined port in the test? Not sure, just a guess. |
Move v8::HandleScope call to Emit removing it from previous locations where it was added to avoid crashing (constructor and destructor of AsyncWrap) for a more general and fool-proof solution. Ref: #19972 (comment) PR-URL: #20045 Reviewed-By: Yang Guo <yangguo@chromium.org> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com>
Move v8::HandleScope call to Emit removing it from previous locations
where it was added to avoid crashing (constructor and destructor of
AsyncWrap) for a more general and fool-proof solution.
Ref: #19972 (comment)
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passescc @addaleax @hashseed