-
Notifications
You must be signed in to change notification settings - Fork 15
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-22 #790
Comments
nodejs-github-bot
pushed a commit
to nodejs/node
that referenced
this issue
Feb 22, 2024
It has failed 22 PRs from the latest 100 CI runs. PR-URL: #51834 Refs: #51822 Refs: nodejs/reliability#790 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
joyeecheung
added a commit
to nodejs/node
that referenced
this issue
Feb 25, 2024
The recursive fs watch tests that mutate the watched folder immediately after fs.watch() returns are all flaking in the CI while the others that mutate the folder with a bit of delay aren't flaking. So this patch adds a bit of delay for the rest of the tests to deflake them. PR-URL: #51842 Refs: nodejs/reliability#790 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
marco-ippolito
pushed a commit
to nodejs/node
that referenced
this issue
Feb 26, 2024
It has failed 22 PRs from the latest 100 CI runs. PR-URL: #51834 Refs: #51822 Refs: nodejs/reliability#790 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
marco-ippolito
pushed a commit
to nodejs/node
that referenced
this issue
Feb 26, 2024
The recursive fs watch tests that mutate the watched folder immediately after fs.watch() returns are all flaking in the CI while the others that mutate the folder with a bit of delay aren't flaking. So this patch adds a bit of delay for the rest of the tests to deflake them. PR-URL: #51842 Refs: nodejs/reliability#790 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
marco-ippolito
pushed a commit
to nodejs/node
that referenced
this issue
Feb 26, 2024
The recursive fs watch tests that mutate the watched folder immediately after fs.watch() returns are all flaking in the CI while the others that mutate the folder with a bit of delay aren't flaking. So this patch adds a bit of delay for the rest of the tests to deflake them. PR-URL: #51842 Refs: nodejs/reliability#790 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
marco-ippolito
pushed a commit
to nodejs/node
that referenced
this issue
Feb 27, 2024
It has failed 22 PRs from the latest 100 CI runs. PR-URL: #51834 Refs: #51822 Refs: nodejs/reliability#790 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
marco-ippolito
pushed a commit
to nodejs/node
that referenced
this issue
Feb 27, 2024
The recursive fs watch tests that mutate the watched folder immediately after fs.watch() returns are all flaking in the CI while the others that mutate the folder with a bit of delay aren't flaking. So this patch adds a bit of delay for the rest of the tests to deflake them. PR-URL: #51842 Refs: nodejs/reliability#790 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
richardlau
pushed a commit
to nodejs/node
that referenced
this issue
Mar 5, 2024
It has failed 22 PRs from the latest 100 CI runs. PR-URL: #51834 Refs: #51822 Refs: nodejs/reliability#790 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
richardlau
pushed a commit
to nodejs/node
that referenced
this issue
Mar 25, 2024
The recursive fs watch tests that mutate the watched folder immediately after fs.watch() returns are all flaking in the CI while the others that mutate the folder with a bit of delay aren't flaking. So this patch adds a bit of delay for the rest of the tests to deflake them. PR-URL: #51842 Refs: nodejs/reliability#790 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
richardlau
pushed a commit
to nodejs/node
that referenced
this issue
Mar 25, 2024
The recursive fs watch tests that mutate the watched folder immediately after fs.watch() returns are all flaking in the CI while the others that mutate the folder with a bit of delay aren't flaking. So this patch adds a bit of delay for the rest of the tests to deflake them. PR-URL: #51842 Refs: nodejs/reliability#790 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@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
It has failed 22 PRs from the latest 100 CI runs. PR-URL: nodejs#51834 Refs: nodejs#51822 Refs: nodejs/reliability#790 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
rdw-msft
pushed a commit
to rdw-msft/node
that referenced
this issue
Mar 26, 2024
The recursive fs watch tests that mutate the watched folder immediately after fs.watch() returns are all flaking in the CI while the others that mutate the folder with a bit of delay aren't flaking. So this patch adds a bit of delay for the rest of the tests to deflake them. PR-URL: nodejs#51842 Refs: nodejs/reliability#790 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@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/57179 to node-test-pull-request/57277 that failed 2 or more PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md
)Jenkins Failure
Backing channel 'JNLP4-connect connection from ... is disconnected.
Example
Build timed out (after 30 minutes). Marking the build as failed.
Example
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
Example
parallel/test-http2-large-write-multiple-requests
Example
parallel/test-fs-watch-recursive-add-file-to-existing-subfolder
Example
parallel/test-fs-watch-recursive-add-file-to-new-folder
Example
parallel/test-buffer-constructor-node-modules-paths
Example
parallel/test-child-process-exec-encoding
Example
parallel/test-child-process-exec-maxbuf
Example
parallel/test-fs-read-stream-concurrent-reads
Example
parallel/test-zlib-brotli-16GB
Example
pummel/test-crypto-timing-safe-equal-benchmarks
Example
parallel/test-child-process-execfile
Example
parallel/test-blob-file-backed
Example
parallel/test-child-process-flush-stdio
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-runner-output
Example
parallel/test-worker-nearheaplimit-deadlock
Example
Progress
Backing channel 'JNLP4-connect connection from ... is disconnected.
(2)Build timed out (after 30 minutes). Marking the build as failed.
(2)fatal: No rebase in progress?
(5)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
(22)parallel/test-child-process-fork-net
(14)parallel/test-fs-watch-recursive-add-file
(11)parallel/test-http2-large-write-multiple-requests
(8)parallel/test-fs-watch-recursive-add-file-to-existing-subfolder
(7)parallel/test-fs-watch-recursive-add-file-to-new-folder
(5)parallel/test-buffer-constructor-node-modules-paths
(4)parallel/test-child-process-exec-encoding
(4)parallel/test-child-process-exec-maxbuf
(4)parallel/test-fs-read-stream-concurrent-reads
(4)parallel/test-zlib-brotli-16GB
(4)pummel/test-crypto-timing-safe-equal-benchmarks
(4)parallel/test-child-process-execfile
(3)parallel/test-blob-file-backed
(2)parallel/test-child-process-flush-stdio
(2)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-runner-output
(2)parallel/test-worker-nearheaplimit-deadlock
(2)The text was updated successfully, but these errors were encountered: