CI Reliability 2025-07-22
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/67994 to node-test-pull-request/68091 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-07-22.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-07-22 00:13 | 0 | 0 | 27 | 1 | 72 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-07-22.md to see failure details
Progress
-
wasi/test-wasi(14) -
wpt/test-web-locks(10) -
parallel/test-http-outgoing-end-cork(9) -
parallel/test-worker-message-port-transfer-filehandle(8) -
parallel/test-runner-mock-timers-scheduler(7) -
parallel/test-fs-watch-recursive-delete(6) -
parallel/test-http-keep-alive-empty-line(6) -
parallel/test-watch-mode-files_watcher(6) -
sequential/test-fs-watch(6) -
es-module/test-vm-contextified-script-leak(5) -
parallel/test-stream-readable-to-web(5) -
pummel/test-fs-watch-non-recursive(5) -
sequential/test-watch-mode-watch-flags(5) -
es-module/test-esm-wasm(4) -
module-hooks/test-module-hooks-import-wasm(4) -
parallel/test-blob(4) -
parallel/test-http-server-headers-timeout-keepalive(4) -
parallel/test-messageevent-brandcheck(4) -
parallel/test-websocket(4) -
sequential/test-tls-session-timeout(4) -
wasi/test-wasi-exitcode(4) -
client-proxy/test-https-proxy-request-handshake-failure(3) -
es-module/test-esm-extensionless-esm-and-wasm(3) -
es-module/test-esm-type-flag-package-scopes(3) -
parallel/test-blocklist-clone(3) -
parallel/test-crypto-x509(3) -
parallel/test-diagnostics-channel-module-import(3) -
parallel/test-eventsource(3) -
parallel/test-inspector-network-fetch(3) -
parallel/test-messaging-marktransfermode(3) -
parallel/test-node-output-eval(3) -
parallel/test-repl-context(3) -
parallel/test-repl-no-terminal(3) -
parallel/test-repl-preview(3) -
parallel/test-repl-setprompt(3) -
parallel/test-repl-syntax-error-stack(3) -
parallel/test-repl-uncaught-exception-async(3) -
parallel/test-repl-underscore(3) -
parallel/test-runner-output(3) -
parallel/test-socketaddress(3) -
parallel/test-webstreams-clone-unref(3) -
sequential/test-debug-prompt(3) -
sequential/test-performance-eventloopdelay(3) -
wasi/test-wasi-io(3) -
client-proxy/test-https-proxy-request-connection-refused(2) -
es-module/test-esm-type-flag-loose-files(2) -
es-module/test-typescript(2) -
es-module/test-wasm-memory-out-of-bound(2) -
es-module/test-wasm-simple(2) -
parallel/test-async-context-frame(2) -
parallel/test-child-process-prototype-tampering(2) -
parallel/test-http-client-close-with-default-agent(2) -
parallel/test-repl-definecommand(2) -
parallel/test-repl-domain(2) -
parallel/test-repl-function-definition-edge-case(2) -
parallel/test-repl-inspector(2) -
parallel/test-repl-load-multiline(2) -
parallel/test-repl-load-multiline-no-trailing-newline(2) -
parallel/test-repl-multiline(2) -
parallel/test-repl-null(2) -
parallel/test-repl-null-thrown(2) -
parallel/test-repl-pretty-stack-custom-writer(2) -
parallel/test-repl-require-cache(2) -
parallel/test-repl-tab(2) -
parallel/test-repl-tab-complete-crash(2) -
parallel/test-repl-tab-complete-on-editor-mode(2) -
parallel/test-repl-uncaught-exception(2) -
parallel/test-structuredClone-global(2) -
parallel/test-webstream-structured-clone-no-leftovers(2) -
parallel/test-worker-broadcastchannel-wpt(2) -
parallel/test-worker-message-event(2) -
parallel/test-worker-message-mark-as-uncloneable(2) -
parallel/test-worker-message-port-transfer-self(2) -
wasi/test-return-on-exit(2) -
wasi/test-wasi-symlinks(2) -
Build timed out (after 30 minutes). Marking the build as failed.(14) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(8) -
fatal: No rebase in progress?(6) -
Failed to trigger node-test-commit(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 reports/2025-07-22.md and the linked CI runs for the failure details. Review the listed tests and infrastructure errors, then identify their causes and update the Progress checklist as each recurring failure is resolved. Done means the reported CI failures have been investigated and the corresponding checklist items are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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