CI Reliability 2025-07-26
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/68109 to node-test-pull-request/68204 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-07-26.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-07-26 00:12 | 4 | 0 | 20 | 2 | 74 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-07-26.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(8) -
Build timed out (after 30 minutes). Marking the build as failed.(4) -
ERROR: Error fetching remote repo 'origin'(3) -
fatal: No rebase in progress?(10) -
Failed to trigger node-test-commit(3) -
wasi/test-wasi(18) -
wpt/test-web-locks(11) -
es-module/test-esm-extensionless-esm-and-wasm(10) -
es-module/test-esm-type-flag-loose-files(10) -
es-module/test-esm-type-flag-package-scopes(10) -
es-module/test-esm-wasm(10) -
parallel/test-node-output-eval(10) -
parallel/test-worker-broadcastchannel-wpt(10) -
wasi/test-wasi-exitcode(10) -
parallel/test-crypto-x509(9) -
parallel/test-repl-mode(9) -
parallel/test-worker-message-event(9) -
parallel/test-worker-message-mark-as-uncloneable(9) -
parallel/test-worker-message-port-transfer-filehandle(8) -
parallel/test-eventsource(7) -
parallel/test-http-keep-alive-empty-line(7) -
parallel/test-messaging-marktransfermode(7) -
parallel/test-process-get-builtin(7) -
parallel/test-repl-tab(7) -
parallel/test-structuredClone-global(7) -
parallel/test-websocket(7) -
parallel/test-webstreams-clone-unref(7) -
es-module/test-vm-contextified-script-leak(6) -
es-module/test-wasm-memory-out-of-bound(6) -
parallel/test-abortsignal-cloneable(6) -
parallel/test-filehandle-autoclose(6) -
parallel/test-repl-require(6) -
parallel/test-repl-tab-complete-import(6) -
parallel/test-repl-throw-null-or-undefined(6) -
parallel/test-worker-load-file-with-extension-other-than-js(6) -
wasi/test-wasi-initialize-validation(6) -
es-module/test-typescript(5) -
parallel/test-diagnostics-channel-module-import(5) -
parallel/test-repl-tab-complete-no-warn(5) -
parallel/test-socketaddress(5) -
parallel/test-webstream-structured-clone-no-leftovers(5) -
parallel/test-worker-message-port(5) -
wasi/test-wasi-not-started(5) -
module-hooks/test-module-hooks-import-wasm(4) -
parallel/test-debugger-help(4) -
parallel/test-debugger-scripts(4) -
parallel/test-repl-null(4) -
parallel/test-repl-preview(4) -
parallel/test-repl-preview-newlines(4) -
parallel/test-repl-tab-complete(4) -
parallel/test-repl-uncaught-exception(4) -
parallel/test-worker-message-port-transfer-self(4) -
client-proxy/test-https-proxy-request-handshake-failure(3) -
parallel/test-runner-mock-timers-scheduler(3) -
sequential/test-performance-eventloopdelay(3) -
wpt/test-streams(3) -
parallel/test-http-outgoing-end-cork(2) -
parallel/test-runner-output(2) -
parallel/test-stream-readable-to-web(2) -
parallel/test-without-async-context-frame(2) -
sequential/test-tls-session-timeout(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-26.md and the linked node-test-pull-request Jenkins runs, using the listed failure categories and test names to group the failures. Investigate the affected CI jobs and tests, then confirm that the recurring failures are resolved and the relevant pull requests complete successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100