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 <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Richard Lau <rlau@redhat.com>
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 <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Richard Lau <rlau@redhat.com>
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 <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Richard Lau <rlau@redhat.com>
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 <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Richard Lau <rlau@redhat.com>
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 <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Richard Lau <rlau@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: FailureExample
Jenkins Failure
Git Failure
Build Failure
Failed to trigger sub buildsExample
undefined
UnknownExample
JSTest Failure
parallel/test-single-executable-applicationExample
parallel/test-net-write-fully-async-hex-stringExample
pummel/test-fs-readfile-tostring-failExample
parallel/test-fs-promises-file-handle-readFileExample
parallel/test-fs-readfileExample
parallel/test-net-write-fully-async-bufferExample
es-module/test-esm-loader-http-importsExample
parallel/test-http-remove-connection-header-persists-connectionExample
parallel/test-worker-nearheaplimit-deadlockExample
sequential/test-http2-large-fileExample
parallel/test-child-process-fork-exec-pathExample
parallel/test-file-write-stream4Example
parallel/test-macos-app-sandboxExample
parallel/test-module-loading-globalpathsExample
parallel/test-runner-watch-modeExample
pummel/test-crypto-timing-safe-equal-benchmarksExample
pummel/test-net-throttleExample
sequential/test-worker-profExample
parallel/test-http2-misbehaving-multiplexExample
parallel/test-inspector-exceptionExample
parallel/test-tls-ticket-clusterExample
pummel/test-net-bytes-per-incoming-chunk-overheadExample
wpt/test-encodingExample
wpt/test-timersExample
wpt/test-wasm-webapiExample
wpt/test-webcryptoExample
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: