-
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
process: expose process.features.inspector #25819
Conversation
Instead of using process.config.variables.v8_enable_inspector to detect whether inspector is enabled in the build.
479900c
to
731f799
Compare
test/common/index.js
Outdated
skip('V8 inspector is disabled'); | ||
} | ||
} | ||
|
||
function skipIfInspectorEnabled() { |
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'm not sure it's worth increasing the surface area of common
for this as it's only used in one place?
withoutintl build test failures are because Lines 48 to 70 in 5860614
e.g. not ok 1449 parallel/test-process-features
|
@richardlau Thanks for the analysis, I've removed |
Co-Authored-By: joyeecheung <[email protected]>
Previous fixup didn't get the test.py indentation right. Fixed. CI: https://ci.nodejs.org/job/node-test-pull-request/20499/ |
Landed in c2359bd |
Instead of using process.config.variables.v8_enable_inspector to detect whether inspector is enabled in the build. PR-URL: #25819 Refs: #25343 Reviewed-By: Eugene Ostroukhov <[email protected]> Reviewed-By: Gus Caplan <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
@joyeecheung This also needs to be backported to v11.x manually |
Instead of using process.config.variables.v8_enable_inspector to detect whether inspector is enabled in the build. PR-URL: #25819 Refs: #25343 Reviewed-By: Eugene Ostroukhov <[email protected]> Reviewed-By: Gus Caplan <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
PR-URL: #54982 Refs: aa0308d Refs: 9010f5f Refs: 52a40e0 Refs: b3ef289 Refs: #2564 Refs: #25819 Refs: #27311 Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
PR-URL: #54982 Refs: aa0308d Refs: 9010f5f Refs: 52a40e0 Refs: b3ef289 Refs: #2564 Refs: #25819 Refs: #27311 Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
PR-URL: nodejs#54982 Refs: nodejs@aa0308d Refs: nodejs@9010f5f Refs: nodejs@52a40e0 Refs: nodejs@b3ef289 Refs: nodejs#2564 Refs: nodejs#25819 Refs: nodejs#27311 Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
PR-URL: nodejs#54982 Refs: nodejs@aa0308d Refs: nodejs@9010f5f Refs: nodejs@52a40e0 Refs: nodejs@b3ef289 Refs: nodejs#2564 Refs: nodejs#25819 Refs: nodejs#27311 Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
Instead of using process.config.variables.v8_enable_inspector
to detect whether inspector is enabled in the build.
Refs: #25343
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes