-
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: remove broken debugger scenarios #5532
Conversation
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: nodejs#3156 Refs: nodejs@c16963b9
One more time, this time hopefully without me putting typos in the CI parameters form: |
Raspberry Pi failure is surely unrelated... ...but that won't stop me from running CI again: https://ci.nodejs.org/job/node-test-pull-request/1839/ |
CI is green. (Which I guess is not surprising as the only thing that happens to this code on CI is that it gets linted.) Not sure who would be comfy giving this an LGTM or saying "sorry, no", but let's try the short list of people that:
To wit: @targos @silverwind @orangemocha @rvagg @indutny |
/cc @nodejs/testing |
For background, the tests were moved out of test/simple because they're very flaky (inherently so.) |
lgtm, cut cut cut |
LGTM |
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: #3156 Refs: c16963b9 PR-URL: #5532 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rod Vagg <[email protected]>
Landed in eb3f04d |
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: #3156 Refs: c16963b9 PR-URL: #5532 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rod Vagg <[email protected]>
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: #3156 Refs: c16963b9 PR-URL: #5532 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rod Vagg <[email protected]>
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: #3156 Refs: c16963b9 PR-URL: #5532 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rod Vagg <[email protected]>
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: #3156 Refs: c16963b9 PR-URL: #5532 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rod Vagg <[email protected]>
`test-debug-break-on-uncaught` was hanging on the domain and parse error scenarios. These tests are not run in CI and may have been broken for a very long time. Refs: #3156 Refs: c16963b9 PR-URL: #5532 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rod Vagg <[email protected]>
make -j8 test
(UNIX) orvcbuild test nosign
(Windows) pass withthis change (including linting)?
test-debug-break-on-uncaught
was hanging on the domain and parse errorscenarios. These tests are not run in CI and may have been broken
for a very long time.
Refs: #3156
Refs: c16963b9
It's not clear to me that the two test scenarios removed here are valid. (/cc @bnoordhuis maybe? See c16963b9 for original commit creating the test)
If simple removal is valid, then this test can be subsequently moved to
parallel
so it can be run in CI on a regular basis.