| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
@Trott build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/379/pipeline |
Sorry, something went wrong.
Use `setImmediate()` instead of `setTimeout()` to improve robustness of test-http2-session-timeout. Fixes: nodejs#20628
| const milliseconds = (diff[0] * 1e3 + diff[1] / 1e6); | ||
| if (milliseconds < serverTimeout * 2) { | ||
| setTimeout(makeReq, callTimeout); | ||
| setImmediate(makeReq); |
Sorry, something went wrong.
There was a problem hiding this comment.
All I can suggest is making the server timeout 1000 and the callTimeout 200. The current change makes this test no longer valid.
Sorry, something went wrong.
There was a problem hiding this comment.
D'oh, I totally misread how this test works. Works for me if this actually fixes the flakiness
Sorry, something went wrong.
|
@Trott can we confirm with a stress test? From what I recall of writing this test, launching too many requests was problematic in making the test flaky in a different way. I used to have setTimeout for 1ms which was nearly equivalent to this. Edit: just got home and started it myself https://ci.nodejs.org/job/node-stress-single-test/1973/ |
Sorry, something went wrong.
|
@nodejs/testing |
Sorry, something went wrong.
|
I ran two stress tests and both appear to be green. 🎉 |
Sorry, something went wrong.
Sorry, something went wrong.
|
Resume Build: https://ci.nodejs.org/job/node-test-pull-request/16112/ |
Sorry, something went wrong.
|
Resume build: https://ci.nodejs.org/job/node-test-pull-request/16135/ |
Sorry, something went wrong.
Use `setImmediate()` instead of `setTimeout()` to improve robustness of test-http2-session-timeout. Fixes: nodejs#20628 PR-URL: nodejs#22026 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Jon Moss <me@jonathanmoss.me> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Use `setImmediate()` instead of `setTimeout()` to improve robustness of test-http2-session-timeout. Fixes: #20628 PR-URL: #22026 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Jon Moss <me@jonathanmoss.me> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Use `setImmediate()` instead of `setTimeout()` to improve robustness of test-http2-session-timeout. Fixes: nodejs#20628 PR-URL: nodejs#22026 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Jon Moss <me@jonathanmoss.me> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Use `setImmediate()` instead of `setTimeout()` to improve robustness of test-http2-session-timeout. Fixes: nodejs#20628 PR-URL: nodejs#22026 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Jon Moss <me@jonathanmoss.me> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Use `setImmediate()` instead of `setTimeout()` to improve robustness of test-http2-session-timeout. Fixes: #20628 Backport-PR-URL: #22850 PR-URL: #22026 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Jon Moss <me@jonathanmoss.me> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
| Back | FazBrowse Home | New Git URL |
Use setImmediate() instead of setTimeout() to improve robustness of
test-http2-session-timeout.
Fixes: #20628
Checklist