Skip to content
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: move the debugger tests back to parallel #6246

Closed
wants to merge 1 commit into from

Conversation

santigimeno
Copy link
Member

@santigimeno santigimeno commented Apr 16, 2016

Checklist
  • tests and code linting passes
  • the commit message follows commit guidelines
Affected core subsystem(s)

test

Description of change

Run the debugger with --port=common.PORT to avoid the use of the same
port.

/cc @nodejs/testing

Run the debugger with `--port=common.PORT` to avoid the use of the same
port.
@santigimeno santigimeno added test Issues and PRs related to the tests. debugger labels Apr 16, 2016
@MylesBorins
Copy link
Contributor

@Trott
Copy link
Member

Trott commented Apr 17, 2016

LGTM. CI looks good (known flaky only failure) and make test completes without errors for me.

@addaleax
Copy link
Member

LGTM

1 similar comment
@cjihrig
Copy link
Contributor

cjihrig commented Apr 18, 2016

LGTM

santigimeno added a commit to santigimeno/node that referenced this pull request Apr 18, 2016
Run the debugger with `--port=common.PORT` to avoid the use of the same
port.

PR-URL: nodejs#6246
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@santigimeno
Copy link
Member Author

Thanks for the reviews. Landed in b95160d

@santigimeno santigimeno deleted the test_debugger branch April 18, 2016 15:01
@addaleax
Copy link
Member

👍 Btw, your Commit: email is different from your Author: email in that commit, is that intentional?

@santigimeno
Copy link
Member Author

No it was not :(. I was wondering if I should fix it

@addaleax
Copy link
Member

I don’t think that matters much, I mean, the Author: field is correct and it was just more of a hint that some of your git settings may not be “correct” anyway. 😄

MylesBorins pushed a commit that referenced this pull request Apr 20, 2016
Run the debugger with `--port=common.PORT` to avoid the use of the same
port.

PR-URL: #6246
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@MylesBorins MylesBorins mentioned this pull request Apr 20, 2016
MylesBorins pushed a commit that referenced this pull request Apr 20, 2016
Run the debugger with `--port=common.PORT` to avoid the use of the same
port.

PR-URL: #6246
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@MylesBorins
Copy link
Contributor

@nodejs/testing is this something we want in lts?

@santigimeno
Copy link
Member Author

I would say so. It should land after #6205

MylesBorins pushed a commit that referenced this pull request Apr 21, 2016
Run the debugger with `--port=common.PORT` to avoid the use of the same
port.

PR-URL: #6246
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@MylesBorins
Copy link
Contributor

this should land with 00b2219

joelostrowski pushed a commit to joelostrowski/node that referenced this pull request Apr 25, 2016
Run the debugger with `--port=common.PORT` to avoid the use of the same
port.

PR-URL: nodejs#6246
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
jasnell pushed a commit that referenced this pull request Apr 26, 2016
Run the debugger with `--port=common.PORT` to avoid the use of the same
port.

PR-URL: #6246
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@MylesBorins
Copy link
Contributor

can I request that someone submit a PR backporting 00b2219 and b95160d

santigimeno added a commit to santigimeno/node that referenced this pull request May 18, 2016
Run the debugger with `--port=common.PORT` to avoid the use of the same
port.

PR-URL: nodejs#6246
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@santigimeno
Copy link
Member Author

@thealphanerd #6831

@santigimeno
Copy link
Member Author

For this to be backported it needs 1df84f4 (#6090) which in turn needs c5afd98 (#6071) which needs some work as test-repl-null doesn't pass because of ee7754b (#5388) with should not be backported.
/cc @Trott

@Trott
Copy link
Member

Trott commented May 19, 2016

I'm inclined to suggest that we label this as dont-land-on-v4.x.

@santigimeno
Copy link
Member Author

Agreed. Labeling as dont-land-on-v4.x.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants