Skip to content

Conversation

@fhinkel
Copy link
Member

Checklist
  • make -j4 test (UNIX)
  • commit message follows commit guidelines
Affected core subsystem(s)

deps V8

Description of change

deps: cherry-pick 43547df from V8 upstream that fixes#6883

/cc @nodejs/v8

Original commit message: [crankshaft] Don't inline "dont_crankshaft" functions Crankshaft shouldn't try to inline functions it knows it can't handle. BUG=v8:5033 Review-Url: https://codereview.chromium.org/2000703002 Cr-Commit-Position: refs/heads/master@{nodejs#36417} Fixes: nodejs#6883
@nodejs-github-botnodejs-github-bot added the v8 engine Issues and PRs related to the V8 dependency. label Jul 24, 2016
@mscdexmscdex added the v6.x label Jul 24, 2016
@bnoordhuis
Copy link
Member

LGTM. I'd start the CI for you but the page is timing out.

@targos
Copy link
Member

@fhinkel
Copy link
MemberAuthor

Thanks, didn't pass though.

/home/iojs/build/workspace/node-test-commit-plinux/nodes/ppcbe-ubuntu1404/out/Release/obj.target/node/src/node_main.o: file not recognized: File truncated collect2: error: ld returned 1 exit status 

We've seen this CI problem before. Has anybody re-imaged the machine like @mhdawson suggested?

@ofrobots
Copy link
Contributor

@fhinkel
Copy link
MemberAuthor

OSX and arm failed, but we don't have the output anymore.

V8 CI failed for PPC, https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=ppcbe-ubuntu1404,v8test=v8test/240/console:

ubuntu1404/v8test/v8test/deps/v8/out/ppc64.release/obj.target/tools/gyp/libv8_libplatform.a: error adding symbols: Archive has no index; run ranlib to add one collect2: error: ld returned 1 exit status 

@ofrobots
Copy link
Contributor

@ofrobots
Copy link
Contributor

Power BE was the only failure in the above. Another CI (with rebasing disabled to avoid the merge conflict due to V8 version bump): https://ci.nodejs.org/job/node-test-pull-request/3525/

@ofrobots
Copy link
Contributor

ofrobots commented Aug 4, 2016

Looks green, and LGTM. Will land later today.
EDIT: I will bump the V8 version at landing time.

ofrobots pushed a commit that referenced this pull request Aug 5, 2016
Original commit message: [crankshaft] Don't inline "dont_crankshaft" functions Crankshaft shouldn't try to inline functions it knows it can't handle. BUG=v8:5033 Review-Url: https://codereview.chromium.org/2000703002 Cr-Commit-Position: refs/heads/master@{#36417} Fixes: #6883 PR-URL: #7863 Reviewed-By: bnoordhuis - Ben Noordhuis <[email protected]> Reviewed-By: targos - Michaël Zasso <[email protected]> Reviewed-By: ofrobots - Ali Ijaz Sheikh <[email protected]>
@ofrobots
Copy link
Contributor

Landed as 75b37a6 with V8 version bumped to 5.0.71.60.

@ofrobotsofrobots closed this Aug 5, 2016
@cjihrigcjihrig mentioned this pull request Aug 11, 2016
BethGriggs pushed a commit to ibmruntimes/node that referenced this pull request Aug 18, 2016
Original commit message: [crankshaft] Don't inline "dont_crankshaft" functions Crankshaft shouldn't try to inline functions it knows it can't handle. BUG=v8:5033 Review-Url: https://codereview.chromium.org/2000703002 Cr-Commit-Position: refs/heads/master@{#36417} Fixes: nodejs/node#6883 PR-URL: nodejs/node#7863 Reviewed-By: bnoordhuis - Ben Noordhuis <[email protected]> Reviewed-By: targos - Michaël Zasso <[email protected]> Reviewed-By: ofrobots - Ali Ijaz Sheikh <[email protected]>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v8 engineIssues and PRs related to the V8 dependency.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@fhinkel@bnoordhuis@targos@ofrobots@mscdex@MylesBorins@nodejs-github-bot