test: deflake test-http2-large-write-multiple-requests #51863
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If the server is not referenced, it might go away too soon and the client may not get enough ends for it to close itself, resulting a timeout. This patch updates the test to simply close the server when enough requests have been processed, and keep the server referenced while the test is ongoing. Drive-by: add more logs to facilitate debugging.
nodejs-github-bot
added
needs-ci
|
In recent CI runs this only reproduces on containered builds, which the stress test doesn't cover. Some older reliability reports (e.g. nodejs/reliability#784 from a week ago) suggest that this also reproduces on fedora-latest-x64, rhel8-x64 and ubuntu2204-64, I did a stress test (https://ci.nodejs.org/view/Stress/job/node-stress-single-test/476/) for this branch and another (https://ci.nodejs.org/view/Stress/job/node-stress-single-test/477/) for the main branch, both are green, so I guess we can only verify this using the PR CI. |
|
I don't think it's necessary for the test to unref the server and it's safe to keep it referenced while maintaining the validity of the test (as far as I can tell from CVE-2019-9517 and CVE-2019-9511 descriptions) but cc @nodejs/http2 just in case. |
github-actions
bot
removed
the
request-ci
marco-ippolito
approved these changes
Feb 24, 2024
lpinca
approved these changes
Feb 24, 2024
Co-authored-by: Luigi Pinca <luigipinca@gmail.com>
github-actions
bot
removed
the
request-ci
joyeecheung
added a commit
that referenced
this pull request
Feb 26, 2024
If the server is not referenced, it might go away too soon and the client may not get enough ends for it to close itself, resulting a timeout. This patch updates the test to simply close the server when enough requests have been processed, and keep the server referenced while the test is ongoing. Drive-by: add more logs to facilitate debugging. PR-URL: #51863 Refs: nodejs/reliability#791 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
|
Landed in a4dd041 |
marco-ippolito
pushed a commit
that referenced
this pull request
Feb 26, 2024
If the server is not referenced, it might go away too soon and the client may not get enough ends for it to close itself, resulting a timeout. This patch updates the test to simply close the server when enough requests have been processed, and keep the server referenced while the test is ongoing. Drive-by: add more logs to facilitate debugging. PR-URL: #51863 Refs: nodejs/reliability#791 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
marco-ippolito
pushed a commit
that referenced
this pull request
Feb 26, 2024
If the server is not referenced, it might go away too soon and the client may not get enough ends for it to close itself, resulting a timeout. This patch updates the test to simply close the server when enough requests have been processed, and keep the server referenced while the test is ongoing. Drive-by: add more logs to facilitate debugging. PR-URL: #51863 Refs: nodejs/reliability#791 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
|
Looks like the flake is still there https://ci.nodejs.org/job/node-test-commit-linux/56383/nodes=rhel8-x64/consoleFull We do get some more logs though. It seems the clients and the server are all supposed to be closed. Not sure what else is keeping the process alive.. |
marco-ippolito
pushed a commit
that referenced
this pull request
Feb 27, 2024
If the server is not referenced, it might go away too soon and the client may not get enough ends for it to close itself, resulting a timeout. This patch updates the test to simply close the server when enough requests have been processed, and keep the server referenced while the test is ongoing. Drive-by: add more logs to facilitate debugging. PR-URL: #51863 Refs: nodejs/reliability#791 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Merged
richardlau
pushed a commit
that referenced
this pull request
Mar 25, 2024
If the server is not referenced, it might go away too soon and the client may not get enough ends for it to close itself, resulting a timeout. This patch updates the test to simply close the server when enough requests have been processed, and keep the server referenced while the test is ongoing. Drive-by: add more logs to facilitate debugging. PR-URL: #51863 Refs: nodejs/reliability#791 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
richardlau
pushed a commit
that referenced
this pull request
Mar 25, 2024
If the server is not referenced, it might go away too soon and the client may not get enough ends for it to close itself, resulting a timeout. This patch updates the test to simply close the server when enough requests have been processed, and keep the server referenced while the test is ongoing. Drive-by: add more logs to facilitate debugging. PR-URL: #51863 Refs: nodejs/reliability#791 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
If the server is not referenced, it might go away too soon and the client may not get enough ends for it to close itself, resulting a timeout.
This patch updates the test to simply close the server when enough requests have been processed, and keep the server referenced while the test is ongoing.
Drive-by: add more logs to facilitate debugging.
Refs: nodejs/reliability#791