-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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: refactor test-async-wrap-getasyncid #18727
test: refactor test-async-wrap-getasyncid #18727
Conversation
The problem with this test is unfortunately more than just I have a PR that proposes a potential solution: #18307 but I'm not entirely happy with it so I've marked it as |
@apapirovski thanks for the info. Would you be ok with the changes while keeping the test in |
Yeah, I don't see why not. 👍 |
yeah, this test definitely needs to stay in sequential. the other changes lgtm |
So it does not use `common.PORT` anymore.
d18af51
to
a515ebc
Compare
Updated so it just removes the use of |
Landed in a865e8b |
So it does not use `common.PORT` anymore. PR-URL: #18727 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Anatoli Papirovski <[email protected]>
So it does not use `common.PORT` anymore. PR-URL: nodejs#18727 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Anatoli Papirovski <[email protected]>
So it does not use `common.PORT` anymore. PR-URL: nodejs#18727 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Anatoli Papirovski <[email protected]>
So it does not use `common.PORT` anymore. PR-URL: #18727 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Anatoli Papirovski <[email protected]>
By not using
common.PORT
anymore.Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
test