-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
deps: update V8 to 6.2 #15362
deps: update V8 to 6.2 #15362
Conversation
Greate! |
Will it be semver-major or landed on Node.js 8 LTS? |
Semver-major |
I updated the OP with two main issues. /cc @nodejs/build @nodejs/platform-macos @nodejs/platform-freebsd |
FYI: I built this branch and ran the llnode test suite. All tests passed. |
@targos I've gone ahead and put in request to get all floated patches upstreamed / landed on 6.2 https://chromium-review.googlesource.com/c/v8/v8/+/666925 https://bugs.chromium.org/p/v8/issues/detail?id=6824 |
One more CI job to see if the gclient thing is a real problem or not |
Here is an ABI-Smoker job being run against this current PR... it should break. If it works... we have a problem https://ci.nodejs.org/view/Node.js-citgm/job/citgm-abi-smoker/39/ |
@targos do you think the problems on VS_VERSION=vs2015-x86,label=win2008r2 is a bug in the build script? |
I'll update CI to not use VS2013 for Node 9. |
@mhdawson any idea why ci is breaking during gsync? |
Updated and removed the V8 backports. I think some of them still need to be merged to 6.2? |
I'm talking about the ones linked in #15362 (comment) |
@addaleax I cherry-picked 8403d6b#diff-ff06109b32824fc20fec697f584a42e3 to this PR. Your other cherry-pick is already in 6.2. |
Does anyone have an idea about how we can fix the error with Clang? |
CI: https://ci.nodejs.org/job/node-test-pull-request/10137/ Haven't seen clang errors yet, perhaps they'll surface in above jobs |
You can see the error in the FreeBSD job. OSX is still pending. |
CI changed to not run Node >=9 on VS2013. This fixed the Windows issue in this PR. Here is a Windows CI run: https://ci.nodejs.org/job/node-test-commit-windows-fanned/11804/ |
With V8 6.2 there is one line less in the promise trace. PR-URL: nodejs#15362 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
PR-URL: nodejs#15362 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
PR-URL: nodejs#15362 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Original commit message: avoid constructor inheritance due to compilation issues Constructor inheritance of a templated constructor is causing compilation issues for node.js: https: //github.com/nodejs/pull/15362#issue-257007421 Change-Id: I7d099ff5a1a2fd5b19c11112ddef8fe824e509f7 Reviewed-on: https://chromium-review.googlesource.com/707008 Commit-Queue: Tobias Tebbi <[email protected]> Commit-Queue: Benedikt Meurer <[email protected]> Reviewed-by: Benedikt Meurer <[email protected]> Cr-Commit-Position: refs/heads/master@{#48445} Refs: v8/v8@0f1dfae PR-URL: nodejs#15362 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
With V8 6.2 there is one line less in the promise trace. PR-URL: #15362 Backport-PR-URL: #16413 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
PR-URL: #15362 Backport-PR-URL: #16413 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
PR-URL: #15362 Backport-PR-URL: #16413 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Original commit message: avoid constructor inheritance due to compilation issues Constructor inheritance of a templated constructor is causing compilation issues for node.js: https: //github.com//pull/15362#issue-257007421 Change-Id: I7d099ff5a1a2fd5b19c11112ddef8fe824e509f7 Reviewed-on: https://chromium-review.googlesource.com/707008 Commit-Queue: Tobias Tebbi <[email protected]> Commit-Queue: Benedikt Meurer <[email protected]> Reviewed-by: Benedikt Meurer <[email protected]> Cr-Commit-Position: refs/heads/master@{#48445} Refs: v8/v8@0f1dfae PR-URL: #15362 Backport-PR-URL: #16413 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
I'm opening this early to track the issues that need fixing.
Blocking issuesCompilation failure with Clang (macOS, FreeBSD)https://ci.nodejs.org/job/node-test-commit-osx/12322/nodes=osx1010/consolehttps://ci.nodejs.org/job/node-test-commit-freebsd/11520/nodes=freebsd11-x64/consoleError
Windows test failurehttps://ci.nodejs.org/job/node-test-binary-windows/11061/RUN_SUBSET=0,VS_VERSION=vs2015,label=win2008r2/consoleThis one is because we do not support building addons with VS2013 anymore. We need to stop testing this on Node >=9.0.0.