Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.3k
test: move the debugger tests back to parallel#6246
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
Uh oh!
There was an error while loading. Please reload this page.
Conversation
santigimeno commented Apr 16, 2016 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
Run the debugger with `--port=common.PORT` to avoid the use of the same port.
MylesBorins commented Apr 16, 2016
Trott commented Apr 17, 2016
LGTM. CI looks good (known flaky only failure) and |
addaleax commented Apr 18, 2016
LGTM |
1 similar comment
cjihrig commented Apr 18, 2016
LGTM |
Run the debugger with `--port=common.PORT` to avoid the use of the same port. PR-URL: nodejs#6246 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
santigimeno commented Apr 18, 2016
Thanks for the reviews. Landed in b95160d |
addaleax commented Apr 18, 2016
👍 Btw, your |
santigimeno commented Apr 18, 2016
No it was not :(. I was wondering if I should fix it |
addaleax commented Apr 18, 2016
I don’t think that matters much, I mean, the |
Run the debugger with `--port=common.PORT` to avoid the use of the same port. PR-URL: #6246 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Run the debugger with `--port=common.PORT` to avoid the use of the same port. PR-URL: #6246 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
MylesBorins commented Apr 21, 2016
@nodejs/testing is this something we want in lts? |
santigimeno commented Apr 21, 2016
I would say so. It should land after #6205 |
Run the debugger with `--port=common.PORT` to avoid the use of the same port. PR-URL: #6246 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
MylesBorins commented Apr 21, 2016
this should land with 00b2219 |
Run the debugger with `--port=common.PORT` to avoid the use of the same port. PR-URL: nodejs#6246 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Run the debugger with `--port=common.PORT` to avoid the use of the same port. PR-URL: #6246 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
MylesBorins commented May 17, 2016
Run the debugger with `--port=common.PORT` to avoid the use of the same port. PR-URL: nodejs#6246 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
santigimeno commented May 18, 2016
santigimeno commented May 18, 2016
Trott commented May 19, 2016
I'm inclined to suggest that we label this as |
santigimeno commented May 19, 2016
Agreed. Labeling as |
Checklist
Affected core subsystem(s)
test
Description of change
Run the debugger with
--port=common.PORTto avoid the use of the sameport.
/cc @nodejs/testing