Uh oh!
There was an error while loading. Please reload this page.
src: refactor node options parsers to mitigate MSVC bug - #26280
Conversation
nodejs-github-bot
commented
Feb 23, 2019
@refack sadly an error occured when I tried to trigger a build :( |
refack
commented
Feb 23, 2019
Trott
commented
Feb 23, 2019
@nodejs/build @nodejs/platform-windows This is supposed to fix the current Windows CI problem. |
|
Resume: https://ci.nodejs.org/job/node-test-commit/26104/ (PI1 fail was infra) |
seishun
commented
Feb 24, 2019
Why is this necessary? Isn't #25593 already fixed? |
As you predicted the fix in #25596 was temporary, and the issue came back. The current code in For example https://nodejs.org/download/nightly/v12.0.0-nightly201902247e0ddf66b9/win-x86/ |
addaleax
commented
Feb 25, 2019
If the issue is still a static initialization order thing, It's not obvious to me how some of the changes here (e.g. to Other than that, the code changes here look good to me. It's unfortunate that the code has to be bloated up a bit, but it's clear that fixing a broken build is more important. Do we know what change caused this? Should that have gotten a red CI? (Or is it still only debug builds?) I also can't reproduce this locally on Windows on |
6b14968 to
5cf7ba6CompareReduced some bloat. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
dc38996 to
f3a4e2bCompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
f3a4e2b to
f98b845Comparerefack
commented
Feb 25, 2019
Rebased into two commits (1) bug fix and (2) fix warnings |
251a80b to
57e2c03Comparerefack
commented
Mar 3, 2019
PR-URL: nodejs#26280Fixes: nodejs#25593 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
* header explicit usage, order, and reduce use of `*-inl.h` * pointer -> const reference when possible * no variable recyclicng * `std::begin/end` prefered over `instance.begin/end` * `USE` for explicit unused resaults PR-URL: nodejs#26280Fixes: nodejs#25593 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
57e2c03 to
2c6d94fCompareBridgeAR
commented
Mar 5, 2019
I had to back out this PR from v11.11.0 due to #26322 (comment). Should this be backported? |
This comment has been minimized.
This comment has been minimized.
refack
commented
Mar 14, 2019
Backport PR: #26649 |
PR-URL: nodejs#26280Fixes: nodejs#25593 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
* header explicit usage, order, and reduce use of `*-inl.h` * pointer -> const reference when possible * no variable recyclicng * `std::begin/end` prefered over `instance.begin/end` * `USE` for explicit unused resaults PR-URL: nodejs#26280Fixes: nodejs#25593 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
* header explicit usage, order, and reduce use of `*-inl.h` * pointer -> const reference when possible * no variable recyclicng * `std::begin/end` prefered over `instance.begin/end` * `USE` for explicit unused resaults Backport-PR-URL: #26649 PR-URL: #26280Fixes: #25593 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
* header explicit usage, order, and reduce use of `*-inl.h` * pointer -> const reference when possible * no variable recyclicng * `std::begin/end` prefered over `instance.begin/end` * `USE` for explicit unused resaults Backport-PR-URL: #26649 PR-URL: #26280Fixes: #25593 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>

Simplify
node_optionsAPI, so the compiler bug should not manifest.Should fix current
masterFixes: #25593
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes