-
Notifications
You must be signed in to change notification settings - Fork 11
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
CI Reliability 2024-02-23 #791
Comments
This was referenced Feb 23, 2024
joyeecheung
added a commit
to nodejs/node
that referenced
this issue
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
to nodejs/node
that referenced
this issue
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
to nodejs/node
that referenced
this issue
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
to nodejs/node
that referenced
this issue
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>
richardlau
pushed a commit
to nodejs/node
that referenced
this issue
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
to nodejs/node
that referenced
this issue
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>
rdw-msft
pushed a commit
to rdw-msft/node
that referenced
this issue
Mar 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: nodejs#51863 Refs: nodejs/reliability#791 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Failures in node-test-pull-request/57217 to node-test-pull-request/57308 that failed 2 or more PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md
)Jenkins Failure
Build Failure
fatal: No rebase in progress?
Example
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
Example
CCTest Failure
Value of: (!expectation.read_expected)
Example
JSTest Failure
wasi/test-wasi
Example
parallel/test-child-process-fork-net
Example
parallel/test-fs-watch-recursive-add-file-to-existing-subfolder
Example
parallel/test-fs-watch-recursive-add-file
Example
parallel/test-fs-watch-recursive-add-file-to-new-folder
Example
parallel/test-blob-file-backed
Example
parallel/test-fs-read-stream-concurrent-reads
Example
parallel/test-http2-large-write-multiple-requests
Example
parallel/test-fs-watch-recursive-assert-leaks
Example
parallel/test-fs-watch-recursive-sync-write
Example
parallel/test-fs-watch-recursive-update-file
Example
parallel/test-http-chunk-problem
Example
parallel/test-http2-misbehaving-multiplex
Example
parallel/test-performance-function
Example
parallel/test-runner-output
Example
wpt/test-wasm-webapi
Example
Progress
fatal: No rebase in progress?
(4)ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
(2)Value of: (!expectation.read_expected)
(2)wasi/test-wasi
(23)parallel/test-child-process-fork-net
(12)parallel/test-fs-watch-recursive-add-file-to-existing-subfolder
(9)parallel/test-fs-watch-recursive-add-file
(6)parallel/test-fs-watch-recursive-add-file-to-new-folder
(5)parallel/test-blob-file-backed
(4)parallel/test-fs-read-stream-concurrent-reads
(3)parallel/test-http2-large-write-multiple-requests
(3)parallel/test-fs-watch-recursive-assert-leaks
(2)parallel/test-fs-watch-recursive-sync-write
(2)parallel/test-fs-watch-recursive-update-file
(2)parallel/test-http-chunk-problem
(2)parallel/test-http2-misbehaving-multiplex
(2)parallel/test-performance-function
(2)parallel/test-runner-output
(2)wpt/test-wasm-webapi
(2)The text was updated successfully, but these errors were encountered: