Skip to content

test: remove broken debugger scenarios - #5532

Closed
Trott wants to merge 1 commit into
nodejs:masterfrom
Trott:amirite
Closed

test: remove broken debugger scenarios#5532
Trott wants to merge 1 commit into
nodejs:masterfrom
Trott:amirite

Conversation

@Trott

@TrottTrott commented Mar 2, 2016

Copy link
Copy Markdown
Member
  • Does make -j8 test (UNIX) or vcbuild test nosign (Windows) pass with
    this change (including linting)?
  • Is the commit message formatted according to [CONTRIBUTING.md][0]?

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

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.

`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
@TrottTrott added debugger test Issues and PRs related to the tests. labels Mar 2, 2016
@Trott

Trott commented Mar 3, 2016

Copy link
Copy Markdown
MemberAuthor

One more time, this time hopefully without me putting typos in the CI parameters form:

https://ci.nodejs.org/job/node-test-pull-request/1838/

@Trott

Trott commented Mar 3, 2016

Copy link
Copy Markdown
MemberAuthor

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/

@Trott

Trott commented Mar 4, 2016

Copy link
Copy Markdown
MemberAuthor

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:

  • are active onboarded collaborators
  • have committed to test/debugger

To wit: @targos@silverwind@orangemocha@rvagg@indutny

@TrottTrott mentioned this pull request Mar 4, 2016
@Trott

Trott commented Mar 6, 2016

Copy link
Copy Markdown
MemberAuthor

/cc @nodejs/testing

@bnoordhuis

Copy link
Copy Markdown
Member

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.

For background, the tests were moved out of test/simple because they're very flaky (inherently so.)

@rvagg

rvagg commented Mar 7, 2016

Copy link
Copy Markdown
Member

lgtm, cut cut cut

@jasnell

Copy link
Copy Markdown
Member

LGTM

jasnell pushed a commit that referenced this pull request Mar 7, 2016
`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 <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rod Vagg <r@va.gg>
@jasnell

Copy link
Copy Markdown
Member

Landed in eb3f04d

@jasnelljasnell closed this Mar 7, 2016
@Fishrock123Fishrock123 mentioned this pull request Mar 7, 2016
Fishrock123 pushed a commit that referenced this pull request Mar 8, 2016
`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 <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rod Vagg <r@va.gg>
Fishrock123 pushed a commit that referenced this pull request Mar 8, 2016
`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 <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rod Vagg <r@va.gg>
MylesBorins pushed a commit that referenced this pull request Mar 17, 2016
`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 <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rod Vagg <r@va.gg>
MylesBorins pushed a commit that referenced this pull request Mar 21, 2016
`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 <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rod Vagg <r@va.gg>
MylesBorins pushed a commit that referenced this pull request Mar 21, 2016
`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 <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Rod Vagg <r@va.gg>
@Trott
Trott deleted the amirite branch January 13, 2022 22:42
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@Trott@bnoordhuis@rvagg@jasnell@MylesBorins