CI Reliability 2025-07-27
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/68126 to node-test-pull-request/68224 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-07-27.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-07-27 00:14 | 1 | 0 | 21 | 2 | 76 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-07-27.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(6) -
Build timed out (after 30 minutes). Marking the build as failed.(5) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal: No rebase in progress?(9) -
Failed to trigger node-test-commit(3) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(2) -
wasi/test-wasi(16) -
wpt/test-web-locks(11) -
parallel/test-http-keep-alive-empty-line(8) -
parallel/test-worker-message-port-transfer-filehandle(7) -
sequential/test-performance-eventloopdelay(6) -
es-module/test-vm-contextified-script-leak(5) -
wpt/test-streams(5) -
es-module/test-esm-extensionless-esm-and-wasm(4) -
es-module/test-esm-type-flag-loose-files(4) -
es-module/test-esm-type-flag-package-scopes(4) -
es-module/test-esm-wasm(4) -
es-module/test-typescript(4) -
module-hooks/test-module-hooks-import-wasm(4) -
parallel/test-crypto-x509(4) -
parallel/test-debugger-help(4) -
parallel/test-debugger-scripts(4) -
parallel/test-diagnostics-channel-module-import(4) -
parallel/test-http-outgoing-end-cork(4) -
parallel/test-node-output-eval(4) -
parallel/test-repl-mode(4) -
parallel/test-repl-null(4) -
parallel/test-repl-preview-newlines(4) -
parallel/test-repl-tab-complete(4) -
parallel/test-repl-tab-complete-no-warn(4) -
parallel/test-repl-uncaught-exception(4) -
parallel/test-socketaddress(4) -
parallel/test-webstream-structured-clone-no-leftovers(4) -
parallel/test-worker-broadcastchannel-wpt(4) -
parallel/test-worker-message-event(4) -
parallel/test-worker-message-mark-as-uncloneable(4) -
parallel/test-worker-message-port(4) -
parallel/test-worker-message-port-transfer-self(4) -
wasi/test-wasi-exitcode(4) -
wasi/test-wasi-not-started(4) -
parallel/test-runner-mock-timers-scheduler(3) -
client-proxy/test-https-proxy-request-handshake-failure(2) -
parallel/test-fs-watch-recursive-delete(2) -
parallel/test-repl-preview(2) -
parallel/test-runner-output(2) -
parallel/test-stream-readable-to-web(2) -
parallel/test-without-async-context-frame(2) -
pummel/test-heapdump-http2(2) -
sequential/test-tls-session-timeout(2) -
wpt/test-blob(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-27.md and the linked node-test-pull-request builds to inspect the listed failures. Use the failure categories and test names to identify causes; done means the reported CI failures are addressed and the affected checks pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100