-
Notifications
You must be signed in to change notification settings - Fork 30k
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
test: update windows module load error message #14950
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it's possible that the libuv update gets backported to LTS then I wonder if it it would make it easier for @nodejs/lts if this was included in the libuv update PR but as a separate commit because they have to land together.
This commit is completely independent of the libuv update. However, the opposite is not true. There is no chance of the libuv update being backported without this, because the Windows CI will light up bright red. For that reason, I think it's fine to keep them as separate PRs. Technically, this is an error message change, so it could be considered semver major. However, it comes from a dependency, so Node doesn't really have any control there. |
libuv 1.14.0 includes a fix for the "%1 is not a valid Win32 application" error message. Refs: nodejs#14866 PR-URL: nodejs#14950 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]>
libuv 1.14.0 includes a fix for the "%1 is not a valid Win32 application" error message. Refs: nodejs/node#14866 PR-URL: nodejs/node#14950 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]>
libuv 1.14.0 includes a fix for the "%1 is not a valid Win32 application" error message. Refs: nodejs/node#14866 PR-URL: nodejs/node#14950 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]>
libuv 1.14.0 includes a fix for the "%1 is not a valid Win32 application" error message. Refs: #14866 PR-URL: #14950 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]>
libuv 1.14.0 includes a fix for the "%1 is not a valid Win32 application" error message. Refs: #14866 PR-URL: #14950 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]>
this needs to land with #14866 |
libuv 1.14.0 includes a fix for the "%1 is not a valid Win32 application" error message. Refs: #14866 PR-URL: #14950 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]>
libuv 1.14.0 includes a fix for the "%1 is not a valid Win32 application" error message. Refs: #14866 PR-URL: #14950 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]>
libuv 1.14.0 includes a fix for the "%1 is not a valid Win32 application" error message.
Refs: #14866
Refs: libuv/libuv#1116
cc: @bnoordhuis
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
test