| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
I don’t know the best way forward either, but I think you can feel free to just re-land these now.
Sorry, something went wrong.
|
Ci: https://ci.nodejs.org/job/node-test-pull-request/9441/ |
Sorry, something went wrong.
|
I'm pretty sure those starting with "deps:" are not necessary with 6.0. That's why I didnt include them. |
Sorry, something went wrong.
|
I just built debug on windows without v8: fix debug builds on Windows but on VS2017 |
Sorry, something went wrong.
Adds missing return which fixes debug builds on Windows Fixes: nodejs#13392 Ref: https://codereview.chromium.org/2929993003/ Refs: nodejs#13634 PR-URL: nodejs#14582 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
|
I dropped the deps tests as they are unnecessary @refack did you have a chance to find out if the debug build is working with VS2015? |
Sorry, something went wrong.
Just completed. debug builds on VS2017 & VS2015 without that commit. |
Sorry, something went wrong.
|
Running CI forced to build debug: https://ci.nodejs.org/job/node-test-commit/11515/ |
Sorry, something went wrong.
|
(Previus CI seems like it works reasonalby well, I'm assuming the sporadic compilation failures are related to memory shortage) |
Sorry, something went wrong.
|
Windows debug CI compiles (without patch). |
Sorry, something went wrong.
|
Closing as it appears we do not need these commits |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
There were three missing patches that were included in #13515 that were missed in #14004
It seems like these were missed because they either
a) Directly touch the V8 system and were not upstreamed
or
b) Were backports that did not follow our backport process
I'm not sure the best process for landing these... please advise
/cc @nodejs/v8