test: check and fail inspector-cluster-port-clash#14074
test: check and fail inspector-cluster-port-clash#14074danbev wants to merge 2 commits intonodejs:masterfrom
Conversation
|
Because this is a |
|
FWIW alternatively you could simply add |
|
As for this PR's change, it's a bit too generic. If you want to pursue such a change, I'd rather have a special flag in the test (something like |
Ah great, that would be much simpler. Thanks, I'll update the PR. |
Currently this test fail when configured --without-inspector or --without-ssl as it is expected to fail but the skipIfInspectorDisabled check will exit as if the test was sucessful. This commit checks if inspector support is available and fails the test allowing the test to be skipped.
c28f46e to
2d0d934
Compare
| if (process.config.variables.v8_enable_inspector === 0) { | ||
| // When the V8 inspector is disabled, using either --without-inspector or | ||
| // --without-ssl, this test will not fail which it is expected to do. | ||
| // The following fail will allow this test to be skipped by failing it. |
There was a problem hiding this comment.
Could you add something to this comment about replacing this block with common.skipIfInspectorDisabled() when/if this test is moved out of known_issues.
There was a problem hiding this comment.
Good idea, I'll add a comment about that.
Currently this test fail when configured --without-inspector or --without-ssl as it is expected to fail but the skipIfInspectorDisabled check will exit as if the test was sucessful. This commit checks if inspector support is available and fails the test allowing the test to be skipped. PR-URL: nodejs#14074 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
Currently this test fail when configured --without-inspector or --without-ssl as it is expected to fail but the skipIfInspectorDisabled check will exit as if the test was sucessful. This commit checks if inspector support is available and fails the test allowing the test to be skipped. PR-URL: #14074 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
Currently this test fail when configured --without-inspector or --without-ssl as it is expected to fail but the skipIfInspectorDisabled check will exit as if the test was sucessful. This commit checks if inspector support is available and fails the test allowing the test to be skipped. PR-URL: #14074 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
Currently this test fail when configured --without-inspector or --without-ssl as it is expected to fail but the skipIfInspectorDisabled check will exit as if the test was sucessful. This commit checks if inspector support is available and fails the test allowing the test to be skipped. PR-URL: #14074 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
Currently this test fail when configured --without-inspector or
--without-ssl as it is expected to fail but the skipIfInspectorDisabled
check will exit as if the test was successful.
This commit checks if inspector support is available and fails the test
allowing the test to be skipped.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
test, tools