-
Notifications
You must be signed in to change notification settings - Fork 31k
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
[20.x backport] worker: add postMessageToThread #57101
[20.x backport] worker: add postMessageToThread #57101
Conversation
Review requested:
|
PR-URL: nodejs#53682 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
2e70ecf
to
4e1795f
Compare
@marco-ippolito I have an unrelated error on this PR but all the tests are passing. What shall I do? |
I only see coverage failing which is fine. Can you paste the error? |
@nodejs/platform-windows we are getting a range error on windows
|
This looks like an out of memory error. Did it happen multiple times ? |
Yes, I retried that several times. But it seems not related to my changes. |
Unrelated indeed. the daily v20.x build fails with the same test: https://ci.nodejs.org/view/All/job/node-daily-v20.x-staging/472/ |
So are we good to merge this? |
PR-URL: #53682 Backport-PR-URL: #57101 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Gerhard Stöbich <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
Landed in 73b5c16 |
Backport of 66a635c