-
-
Notifications
You must be signed in to change notification settings - Fork 71
Build broken on Windows (VS2017) #128
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
Comments
/cc @nodejs/platform-windows |
Thought on add visual studio 2017 to github action ? |
Yeap. But I want github action only do the least job. We have jenkins for full CI. |
What kind of information could a github action give us that's not already part of our CI job result? |
Automatically trigger for PR and push. Also the build log won't lost. ci.nodejs.org/job/node-compile-windows/30296/nodes=win-vs2017/console is broken. But I am quite insist on this, we got vs2019 on github action anyway. |
The GitHub runner containing VS2017 is being removed soon:
|
(Also our Windows builds using GitHub Actions are broken at the moment failing to install |
Yeap, there websites is down. |
Looks like this happen multi times microsoft/vcpkg#2777 |
current error on visual studio 2017: [00:41:30] objects-printer-tq.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library [C:\projects\appveyor-playground\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj]
[00:41:30] class-verifiers-tq.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library [C:\projects\appveyor-playground\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj]
[00:41:30] simulator-base.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library [C:\projects\appveyor-playground\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj]
[00:41:30] perf-jit.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library [C:\projects\appveyor-playground\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj]
[00:41:30] objects-debug.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library [C:\projects\appveyor-playground\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj]
[00:41:30] gdb-jit.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library [C:\projects\appveyor-playground\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj]
[00:41:30] tnode.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library [C:\projects\appveyor-playground\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj]
[00:41:30] constant-pool.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library [C:\projects\appveyor-playground\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj]
[00:41:31] v8_base_without_compiler.vcxproj -> ..\..\out\Release\lib\v8_base_without_compiler.lib |
New fix: #143. |
Node.js build fails on VS2017 without these headers, see the downstream issue (nodejs/node-v8#128). Co-authored-by: Ben Noordhuis <[email protected]> Co-authored-by: gengjiawen <[email protected]> Change-Id: I771eab435dce5cf548581f3acd78681180c77692 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2093951 Reviewed-by: Tobias Tebbi <[email protected]> Commit-Queue: Tobias Tebbi <[email protected]> Cr-Commit-Position: refs/heads/master@{#66661}
Original commit message: [torque] fix build on VS2017 Node.js build fails on VS2017 without these headers, see the downstream issue (nodejs/node-v8#128). Co-authored-by: Ben Noordhuis <[email protected]> Co-authored-by: gengjiawen <[email protected]> Change-Id: I771eab435dce5cf548581f3acd78681180c77692 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2093951 Reviewed-by: Tobias Tebbi <[email protected]> Commit-Queue: Tobias Tebbi <[email protected]> Cr-Commit-Position: refs/heads/master@{#66661} Refs: v8/v8@931bdbd
Original commit message: [torque] fix build on VS2017 Node.js build fails on VS2017 without these headers, see the downstream issue (#128). Co-authored-by: Ben Noordhuis <[email protected]> Co-authored-by: gengjiawen <[email protected]> Change-Id: I771eab435dce5cf548581f3acd78681180c77692 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2093951 Reviewed-by: Tobias Tebbi <[email protected]> Commit-Queue: Tobias Tebbi <[email protected]> Cr-Commit-Position: refs/heads/master@{#66661} Refs: v8/v8@931bdbd
Original commit message: [torque] fix build on VS2017 Node.js build fails on VS2017 without these headers, see the downstream issue (#128). Co-authored-by: Ben Noordhuis <[email protected]> Co-authored-by: gengjiawen <[email protected]> Change-Id: I771eab435dce5cf548581f3acd78681180c77692 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2093951 Reviewed-by: Tobias Tebbi <[email protected]> Commit-Queue: Tobias Tebbi <[email protected]> Cr-Commit-Position: refs/heads/master@{#66661} Refs: v8/v8@931bdbd
Original commit message: [torque] fix build on VS2017 Node.js build fails on VS2017 without these headers, see the downstream issue (#128). Co-authored-by: Ben Noordhuis <[email protected]> Co-authored-by: gengjiawen <[email protected]> Change-Id: I771eab435dce5cf548581f3acd78681180c77692 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2093951 Reviewed-by: Tobias Tebbi <[email protected]> Commit-Queue: Tobias Tebbi <[email protected]> Cr-Commit-Position: refs/heads/master@{#66661} Refs: v8/v8@931bdbd
Original commit message: [torque] fix build on VS2017 Node.js build fails on VS2017 without these headers, see the downstream issue (#128). Co-authored-by: Ben Noordhuis <[email protected]> Co-authored-by: gengjiawen <[email protected]> Change-Id: I771eab435dce5cf548581f3acd78681180c77692 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2093951 Reviewed-by: Tobias Tebbi <[email protected]> Commit-Queue: Tobias Tebbi <[email protected]> Cr-Commit-Position: refs/heads/master@{#66661} Refs: v8/v8@931bdbd
Original commit message: [torque] fix build on VS2017 Node.js build fails on VS2017 without these headers, see the downstream issue (nodejs/node-v8#128). Co-authored-by: Ben Noordhuis <[email protected]> Co-authored-by: gengjiawen <[email protected]> Change-Id: I771eab435dce5cf548581f3acd78681180c77692 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2093951 Reviewed-by: Tobias Tebbi <[email protected]> Commit-Queue: Tobias Tebbi <[email protected]> Cr-Commit-Position: refs/heads/master@{#66661} Refs: v8/v8@931bdbd
Original commit message: [torque] fix build on VS2017 Node.js build fails on VS2017 without these headers, see the downstream issue (nodejs/node-v8#128). Co-authored-by: Ben Noordhuis <[email protected]> Co-authored-by: gengjiawen <[email protected]> Change-Id: I771eab435dce5cf548581f3acd78681180c77692 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2093951 Reviewed-by: Tobias Tebbi <[email protected]> Commit-Queue: Tobias Tebbi <[email protected]> Cr-Commit-Position: refs/heads/master@{#66661} Refs: v8/v8@931bdbd
Original commit message: [torque] fix build on VS2017 Node.js build fails on VS2017 without these headers, see the downstream issue (#128). Co-authored-by: Ben Noordhuis <[email protected]> Co-authored-by: gengjiawen <[email protected]> Change-Id: I771eab435dce5cf548581f3acd78681180c77692 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2093951 Reviewed-by: Tobias Tebbi <[email protected]> Commit-Queue: Tobias Tebbi <[email protected]> Cr-Commit-Position: refs/heads/master@{#66661} Refs: v8/v8@931bdbd
Original commit message: [torque] fix build on VS2017 Node.js build fails on VS2017 without these headers, see the downstream issue (#128). Co-authored-by: Ben Noordhuis <[email protected]> Co-authored-by: gengjiawen <[email protected]> Change-Id: I771eab435dce5cf548581f3acd78681180c77692 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2093951 Reviewed-by: Tobias Tebbi <[email protected]> Commit-Queue: Tobias Tebbi <[email protected]> Cr-Commit-Position: refs/heads/master@{#66661} Refs: v8/v8@931bdbd
Original commit message: [torque] fix build on VS2017 Node.js build fails on VS2017 without these headers, see the downstream issue (#128). Co-authored-by: Ben Noordhuis <[email protected]> Co-authored-by: gengjiawen <[email protected]> Change-Id: I771eab435dce5cf548581f3acd78681180c77692 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2093951 Reviewed-by: Tobias Tebbi <[email protected]> Commit-Queue: Tobias Tebbi <[email protected]> Cr-Commit-Position: refs/heads/master@{#66661} Refs: v8/v8@931bdbd
Original commit message: [torque] fix build on VS2017 Node.js build fails on VS2017 without these headers, see the downstream issue (nodejs/node-v8#128). Co-authored-by: Ben Noordhuis <[email protected]> Co-authored-by: gengjiawen <[email protected]> Change-Id: I771eab435dce5cf548581f3acd78681180c77692 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2093951 Reviewed-by: Tobias Tebbi <[email protected]> Commit-Queue: Tobias Tebbi <[email protected]> Cr-Commit-Position: refs/heads/master@{#66661} Refs: v8/v8@931bdbd PR-URL: #32116 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
https://ci.nodejs.org/job/node-compile-windows/30296/nodes=win-vs2017/console
The text was updated successfully, but these errors were encountered: