-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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: fix test-net-throttle #33329
test: fix test-net-throttle #33329
Conversation
Relevant CI run is: https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/14181/ Pummel tests otherwise don't get run in CI, so only the linter and the above job are relevant. |
The test passed in CI. First time in something like two weeks! |
Re-running relevant CI post-fixup commit: https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/14184/ |
This is basically the only thing that has kept node-daily-master from being green many days now. Fast-track? 👍 here to approve if you're a Collaborator. |
Repeat writes until data is queued in memory, rather than assuming that it will happen by a certain point. Fixes: nodejs#33135 PR-URL: nodejs#33329 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
d348f0c
to
5ded044
Compare
Landed in 5ded044 |
Repeat writes until data is queued in memory, rather than assuming that
it will happen by a certain point.
Fixes: #33135
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes