CI Reliability 2024-08-30
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 57
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Failures in node-test-pull-request/61618 to node-test-pull-request/61713 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-08-30.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-08-30 17:13 | 9 | 4 | 17 | 3 | 67 | 4.55% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-08-30.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(8) -
Failed to create a temp file on /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64(6) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
fatal error: Killed signal terminated program cc1plus(11) -
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...(7) -
parallel/test-http2-socket-close(13) -
parallel/test-runner-run-watch(13) -
parallel/test-esm-loader-hooks-inspect-wait(10) -
parallel/test-macos-app-sandbox(6) -
pummel/test-fs-readfile-tostring-fail(5) -
parallel/test-file-write-stream4(4) -
parallel/test-module-loading-globalpaths(4) -
parallel/test-runner-watch-mode-complex(4) -
sequential/test-http-server-request-timeouts-mixed(4) -
parallel/test-child-process-fork-exec-path(3) -
parallel/test-http-get-pipeline-problem(3) -
parallel/test-runner-output(3) -
wpt/test-structured-clone(3) -
parallel/test-debugger-heap-profiler(2) -
parallel/test-fs-utimes(2) -
parallel/test-performance-function(2) -
parallel/test-runner-coverage(2) -
parallel/test-runner-coverage-thresholds(2) -
parallel/test-runner-run(2) -
parallel/test-runner-test-filepath(2) -
parallel/test-runner-test-fullname(2) -
parallel/test-runner-typechecking(2) -
parallel/test-runner-v8-deserializer(2) -
parallel/test-set-http-max-http-headers(2) -
parallel/test-sqlite(2) -
parallel/test-sqlite-data-types(2) -
parallel/test-sqlite-database-sync(2) -
parallel/test-sqlite-named-parameters(2) -
parallel/test-sqlite-statement-sync(2) -
parallel/test-sqlite-transactions(2) -
parallel/test-stdout-stderr-write(2) -
parallel/test-stream2-httpclient-response-end(2) -
parallel/test-stream2-large-read-stall(2) -
parallel/test-stream2-push(2) -
parallel/test-stream3-pause-then-read(2) -
parallel/test-tcp-wrap-listen(2) -
parallel/test-timers-unref-remove-other-unref-timers(2) -
parallel/test-timers-unref-remove-other-unref-timers-only-one-fires(2) -
parallel/test-tls-cli-max-version-1.2(2) -
parallel/test-tls-cli-max-version-1.3(2) -
parallel/test-tls-cli-min-version-1.0(2) -
parallel/test-tls-cli-min-version-1.1(2) -
parallel/test-tls-cli-min-version-1.2(2) -
parallel/test-tls-cli-min-version-1.3(2) -
parallel/test-tls-client-reject-12(2) -
parallel/test-tls-client-resume-12(2) -
parallel/test-tls-enable-trace(2) -
parallel/test-tls-min-max-version(2) -
parallel/test-tls-pause(2) -
parallel/test-tls-set-encoding(2) -
parallel/test-trace-events-dynamic-enable-workers-disabled(2) -
parallel/test-trace-events-get-category-enabled-buffer(2) -
parallel/test-worker-exit-heapsnapshot(2) -
parallel/test-worker-message-not-serializable(2) -
parallel/test-worker-message-port-drain(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
parallel/test-worker-track-unmanaged-fds(2) -
pseudo-tty/test-stdin-write(2) -
pseudo-tty/test-trace-sigint-on-idle(2) -
pummel/test-net-pingpong(2) -
pummel/test-net-write-callbacks(2) -
pummel/test-regress-GH-892(2) -
pummel/test-stream-pipe-multi(2) -
pummel/test-timers(2) -
report/test-report-exclude-network(2) -
sequential/test-deprecation-flags(2) -
sequential/test-http-econnrefused(2) -
sequential/test-net-GH-5504(2) -
sequential/test-net-connect-econnrefused(2) -
sequential/test-repl-timeout-throw(2) -
sequential/test-single-executable-application-empty(2) -
wasi/test-wasi(2) -
wpt/test-atob(2) -
wpt/test-blob(2) -
wpt/test-broadcastchannel(2) -
wpt/test-compression(2) -
wpt/test-console(2) -
wpt/test-domexception(2) -
wpt/test-encoding(2) -
wpt/test-events(2) -
wpt/test-performance-timeline(2) -
wpt/test-resource-timing(2) -
wpt/test-streams(2) -
wpt/test-timers(2) -
wpt/test-url(2) -
wpt/test-wasm-webapi(2) -
wpt/test-webcrypto(2) -
wpt/test-webstorage(2)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked CI jobs and the report at reports/2024-08-30.md, then review the recurring failures listed under Progress. Determine which failures are actionable and group them by cause; done means the identified CI failures are addressed and the relevant jobs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100