-
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: make test-worker-prof more robust #49274
Conversation
097acb3
to
c5d821d
Compare
Stress test on Windows 2022 + VS 2019 https://ci.nodejs.org/job/node-stress-single-test/418/ |
c5d821d
to
d966328
Compare
Looks like it can still be flaky with the current workload. Switching to a time-based workload... |
Another stress test on more platforms: https://ci.nodejs.org/job/node-stress-single-test/420/ |
Updated the workload a bit, this seems to guarantee ~1000 ticks on both the parent and the worker. |
7779fab
to
5c66341
Compare
Another stress test: https://ci.nodejs.org/job/node-stress-single-test/422/ |
Use a JS workload instead of repeating FS operations and use a timer to make it less flaky on machines with little resources.
5c66341
to
0d3a6f2
Compare
Looks like the CI is having trouble rebasing the PR. Manually rebased instead. |
Landed in 7f001c2 |
Use a JS workload instead of repeating FS operations and use a timer to make it less flaky on machines with little resources. PR-URL: #49274 Refs: #26401 Refs: nodejs/reliability#640 Reviewed-By: Benjamin Gruenbaum <[email protected]>
Use a JS workload instead of repeating FS operations and use a timer to make it less flaky on machines with little resources. PR-URL: nodejs#49274 Refs: nodejs#26401 Refs: nodejs/reliability#640 Reviewed-By: Benjamin Gruenbaum <[email protected]>
Use a JS workload instead of repeating FS operations to make it less flaky on machines with little resources.
Refs: #26401
Refs: nodejs/reliability#640