-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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: skipIfInspectorDisabled cluster-inspect-brk #12757
test: skipIfInspectorDisabled cluster-inspect-brk #12757
Conversation
@@ -1,5 +1,9 @@ | |||
'use strict'; | |||
const common = require('../common'); | |||
if (!common.hasCrypto) { |
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.
I think it can just be common.skipIfInspectorDisabled()
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.
IMHO not having SSL is not a reason to skip this test, that's a regression.
What @targos suggested makes more sense, and should be reflected in title and commit message, i.e. test: skip cluster-inspect-brk if inspector is disabled
Good point, I'll fix that. Thanks
sön 30 apr. 2017 kl. 12:53 skrev Michaël Zasso <notifications@github.com>:
… ***@***.**** commented on this pull request.
------------------------------
In test/sequential/test-cluster-inspect-brk.js
<#12757 (comment)>:
> @@ -1,5 +1,9 @@
'use strict';
const common = require('../common');
+if (!common.hasCrypto) {
I think it can just be common.skipIfInspectorDisabled()
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#12757 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAaY32C-hCXevPx7VykTQUmHl-UcxT6Zks5r1GgigaJpZM4NMe75>
.
|
Is it the same with just Ref: #12758 |
@@ -1,5 +1,9 @@ | |||
'use strict'; | |||
const common = require('../common'); | |||
if (!common.hasCrypto) { |
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.
IMHO not having SSL is not a reason to skip this test, that's a regression.
What @targos suggested makes more sense, and should be reflected in title and commit message, i.e. test: skip cluster-inspect-brk if inspector is disabled
When configured --without-ssl the inspect-brk option will not be available and the process will exit with a exit value of 9 "Invalid Argument/Bad option". This commit adds a skipIfInspectorDisabled check since --without-ssl implies that no inspector support is build as well.
342e8e8
to
2cb2411
Compare
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.
Thanks.
When configured --without-ssl the inspect-brk option will not be available and the process will exit with a exit value of 9 "Invalid Argument/Bad option". This commit adds a skipIfInspectorDisabled check since --without-ssl implies that no inspector support is build as well. PR-URL: nodejs#12757 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Landed in 10ccf56 |
When configured --without-ssl the inspect-brk option will not be available and the process will exit with a exit value of 9 "Invalid Argument/Bad option". This commit adds a skipIfInspectorDisabled check since --without-ssl implies that no inspector support is build as well. PR-URL: nodejs#12757 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Should land with #12615 |
When configured --without-ssl the inspect-brk option will not be available and the process will exit with a exit value of 9 "Invalid Argument/Bad option". This commit adds a skipIfInspectorDisabled check since --without-ssl implies that no inspector support is build as well. PR-URL: #12757 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
When configured --without-ssl the inspect-brk option will not be available and the process will exit with a exit value of 9 "Invalid Argument/Bad option". This commit adds a skipIfInspectorDisabled check since --without-ssl implies that no inspector support is build as well. PR-URL: #12757 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
When configured --without-ssl the inspect-brk option will not be
available and the process will exit with a exit value of 9 "Invalid
Argument/Bad option".
This commit adds a skipIfInspectorDisabled check since --without-ssl
implies that no inspector support is build as well.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
src