-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
doc: corrected vcbuild parameters for testing on windows #10112
Conversation
Corrected parameter for running tests on Windows. Without the corrected parameters, Windows users encounter an error about failing to sign the build, "Failed to sign exe", which can be discouraging to new Windows community members.
@nodejs/platform-windows |
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.
LGTM, although I'd prefer vcbuild nosign test
.
I think this would be made unnecessary by #10156, which will also stop people having to remember the |
#10156 landed. Is this still necessary? |
@jasnell #10156 was +1 for
EDIT: we should be using cc/ @joaocgreis |
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.
LGTM for v[4,6,7].
If this is a backport for 7, 6 and 4, then, separate PRs for landing in those should be opened. |
I'm thinking that #10156 now makes this PR un-necessary. |
@jboarman see #10112 (comment), it's necessary for all current release lines as that PR is |
Checklist
make -j8 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
doc
Description of change
Corrected parameter for running tests on Windows. Without the corrected
parameters, Windows users encounter an error about failing to sign the
build, "Failed to sign exe", which can be discouraging to new Windows
community members.