-
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 2023-04-28 #549
Comments
tniessen
added a commit
to tniessen/node
that referenced
this issue
Apr 28, 2023
In general, we assume that the tmpdir will provide sufficient space for most tests. Some tests, however, require hundreds of megabytes or even gigabytes of space, which often causes them to fail, especially on our macOS infrastructure. The most recent reliability report contains more than 20 related CI failures. This change adds a new function hasTooLittleSpace() to the tmpdir module that uses statfsSync() to guess whether allocating a certain amount of space within the temporary directory will fail. This change also updates the most frequently failing tests to use the new function, in which case the relevant parts of the tests are skipped. Refs: nodejs/reliability#549
tniessen
added a commit
to tniessen/node
that referenced
this issue
Apr 29, 2023
In general, we assume that the tmpdir will provide sufficient space for most tests. Some tests, however, require hundreds of megabytes or even gigabytes of space, which often causes them to fail, especially on our macOS infrastructure. The most recent reliability report contains more than 20 related CI failures. This change adds a new function hasTooLittleSpace() to the tmpdir module that uses statfsSync() to guess whether allocating a certain amount of space within the temporary directory will fail. This change also updates the most frequently failing tests to use the new function, in which case the relevant parts of the tests are skipped. Refs: nodejs/reliability#549
tniessen
added a commit
to tniessen/node
that referenced
this issue
Apr 30, 2023
In general, we assume that the tmpdir will provide sufficient space for most tests. Some tests, however, require hundreds of megabytes or even gigabytes of space, which often causes them to fail, especially on our macOS infrastructure. The most recent reliability report contains more than 20 related CI failures. This change adds a new function hasEnoughSpace() to the tmpdir module that uses statfsSync() to guess whether allocating a certain amount of space within the temporary directory will succeed. This change also updates the most frequently failing tests to use the new function such that the relevant parts of the tests are skipped if tmpdir has insufficient space. Refs: nodejs/reliability#549
nodejs-github-bot
pushed a commit
to nodejs/node
that referenced
this issue
May 1, 2023
In general, we assume that the tmpdir will provide sufficient space for most tests. Some tests, however, require hundreds of megabytes or even gigabytes of space, which often causes them to fail, especially on our macOS infrastructure. The most recent reliability report contains more than 20 related CI failures. This change adds a new function hasEnoughSpace() to the tmpdir module that uses statfsSync() to guess whether allocating a certain amount of space within the temporary directory will succeed. This change also updates the most frequently failing tests to use the new function such that the relevant parts of the tests are skipped if tmpdir has insufficient space. Refs: nodejs/reliability#549 PR-URL: #47767 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Richard Lau <[email protected]>
targos
pushed a commit
to nodejs/node
that referenced
this issue
May 2, 2023
In general, we assume that the tmpdir will provide sufficient space for most tests. Some tests, however, require hundreds of megabytes or even gigabytes of space, which often causes them to fail, especially on our macOS infrastructure. The most recent reliability report contains more than 20 related CI failures. This change adds a new function hasEnoughSpace() to the tmpdir module that uses statfsSync() to guess whether allocating a certain amount of space within the temporary directory will succeed. This change also updates the most frequently failing tests to use the new function such that the relevant parts of the tests are skipped if tmpdir has insufficient space. Refs: nodejs/reliability#549 PR-URL: #47767 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Richard Lau <[email protected]>
targos
pushed a commit
to nodejs/node
that referenced
this issue
May 3, 2023
In general, we assume that the tmpdir will provide sufficient space for most tests. Some tests, however, require hundreds of megabytes or even gigabytes of space, which often causes them to fail, especially on our macOS infrastructure. The most recent reliability report contains more than 20 related CI failures. This change adds a new function hasEnoughSpace() to the tmpdir module that uses statfsSync() to guess whether allocating a certain amount of space within the temporary directory will succeed. This change also updates the most frequently failing tests to use the new function such that the relevant parts of the tests are skipped if tmpdir has insufficient space. Refs: nodejs/reliability#549 PR-URL: #47767 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Richard Lau <[email protected]>
danielleadams
pushed a commit
to nodejs/node
that referenced
this issue
Jul 6, 2023
In general, we assume that the tmpdir will provide sufficient space for most tests. Some tests, however, require hundreds of megabytes or even gigabytes of space, which often causes them to fail, especially on our macOS infrastructure. The most recent reliability report contains more than 20 related CI failures. This change adds a new function hasEnoughSpace() to the tmpdir module that uses statfsSync() to guess whether allocating a certain amount of space within the temporary directory will succeed. This change also updates the most frequently failing tests to use the new function such that the relevant parts of the tests are skipped if tmpdir has insufficient space. Refs: nodejs/reliability#549 PR-URL: #47767 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Richard Lau <[email protected]>
MoLow
pushed a commit
to MoLow/node
that referenced
this issue
Jul 6, 2023
In general, we assume that the tmpdir will provide sufficient space for most tests. Some tests, however, require hundreds of megabytes or even gigabytes of space, which often causes them to fail, especially on our macOS infrastructure. The most recent reliability report contains more than 20 related CI failures. This change adds a new function hasEnoughSpace() to the tmpdir module that uses statfsSync() to guess whether allocating a certain amount of space within the temporary directory will succeed. This change also updates the most frequently failing tests to use the new function such that the relevant parts of the tests are skipped if tmpdir has insufficient space. Refs: nodejs/reliability#549 PR-URL: nodejs#47767 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Richard Lau <[email protected]>
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/51420 to node-test-pull-request/51517 that failed more than 2 PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md
)CCTest Failure
../test/cctest/test_inspector_socket.cc:323: Failure
Example
Jenkins Failure
Git Failure
Build Failure
Failed to trigger sub builds
Example
undefined
Unknown
Example
JSTest Failure
parallel/test-single-executable-application
Example
parallel/test-net-write-fully-async-hex-string
Example
pummel/test-fs-readfile-tostring-fail
Example
parallel/test-fs-promises-file-handle-readFile
Example
parallel/test-fs-readfile
Example
parallel/test-net-write-fully-async-buffer
Example
es-module/test-esm-loader-http-imports
Example
parallel/test-http-remove-connection-header-persists-connection
Example
parallel/test-worker-nearheaplimit-deadlock
Example
sequential/test-http2-large-file
Example
parallel/test-child-process-fork-exec-path
Example
parallel/test-file-write-stream4
Example
parallel/test-macos-app-sandbox
Example
parallel/test-module-loading-globalpaths
Example
parallel/test-runner-watch-mode
Example
pummel/test-crypto-timing-safe-equal-benchmarks
Example
pummel/test-net-throttle
Example
sequential/test-worker-prof
Example
parallel/test-http2-misbehaving-multiplex
Example
parallel/test-inspector-exception
Example
parallel/test-tls-ticket-cluster
Example
pummel/test-net-bytes-per-incoming-chunk-overhead
Example
wpt/test-encoding
Example
wpt/test-timers
Example
wpt/test-wasm-webapi
Example
wpt/test-webcrypto
Example
Progress
../test/cctest/test_inspector_socket.cc:323: Failure
(6)Failed to trigger sub builds
(3)Unknown
(2)parallel/test-single-executable-application
(14)parallel/test-net-write-fully-async-hex-string
(13)pummel/test-fs-readfile-tostring-fail
(13)parallel/test-fs-promises-file-handle-readFile
(7)parallel/test-fs-readfile
(7)parallel/test-net-write-fully-async-buffer
(7)es-module/test-esm-loader-http-imports
(4)parallel/test-http-remove-connection-header-persists-connection
(4)parallel/test-worker-nearheaplimit-deadlock
(4)sequential/test-http2-large-file
(4)parallel/test-child-process-fork-exec-path
(3)parallel/test-file-write-stream4
(3)parallel/test-macos-app-sandbox
(3)parallel/test-module-loading-globalpaths
(3)parallel/test-runner-watch-mode
(3)pummel/test-crypto-timing-safe-equal-benchmarks
(3)pummel/test-net-throttle
(3)sequential/test-worker-prof
(3)parallel/test-http2-misbehaving-multiplex
(2)parallel/test-inspector-exception
(2)parallel/test-tls-ticket-cluster
(2)pummel/test-net-bytes-per-incoming-chunk-overhead
(2)wpt/test-encoding
(2)wpt/test-timers
(2)wpt/test-wasm-webapi
(2)wpt/test-webcrypto
(2)The text was updated successfully, but these errors were encountered: