-
-
Notifications
You must be signed in to change notification settings - Fork 33.6k
refactor away test/inspector #16197
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
refactor away test/inspector #16197
Conversation
|
@nodejs/v8-inspector |
|
@maclover7 A third bullet point might be "evaluate if any of these tests can/should be moved to parallel". |
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 with a request.
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.
You could use common.fixtures.path('inspector-global-function.js') here.
Makefile
Outdated
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.
Can you also remove it from vcbuild.bat? (Two mentions.)
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.
Need the FLAKY flags moved as well
test/inspector/inspector.status
Outdated
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.
Shouldn't these be moved to test/parallel/parallel.status
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.
Good catch -- thank you!
|
Several related failures in CI, including linting issues. |
|
@jasnell fixed linter issue and moved one of the tests to sequential, would you be willing to run CI again? |
* remove inspector directory artifacts PR-URL: nodejs#16197 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]>
|
Landed in 978629c 10x! 🎉 |
* remove inspector directory artifacts PR-URL: #16197 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]>
* remove inspector directory artifacts PR-URL: nodejs/node#16197 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: James M Snell <[email protected]>
|
Cross-ref: #16281 |
Refs: #13622, cc @Trott @refack
Tried to handle as much as I could in this PR, but there here are some things I'd like to handle in separate PRs:
inspector-helper.jsto a proper "common" module (write basic docs, etc.)test/inspectorare gonetest/parallelChecklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
test