CI Reliability 2026-04-25
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/72815 to node-test-pull-request/72903 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-25.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-25 00:23 | 9 | 11 | 13 | 1 | 66 | 12.22% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-25.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal: No rebase in progress?(3) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(2) -
Failed to trigger fanned build(2) -
parallel/test-debugger-probe-json-preview(10) -
wpt/test-wasm-jsapi(9) -
parallel/test-debugger-probe-child-inspect-port-zero(8) -
parallel/test-debugger-probe-miss(8) -
wpt/test-hr-time(7) -
parallel/test-debugger-probe-global-option-order(6) -
parallel/test-debugger-probe-json(6) -
parallel/test-debugger-probe-json-special-values(6) -
parallel/test-debugger-probe-text(5) -
sequential/test-watch-mode-restart-esm-loading-error(5) -
test-runner/test-run-watch-dependency-repeatedly(5) -
test-runner/test-run-watch-without-file(5) -
test-runner/test-run-watch-cwd-isolation-none(4) -
test-runner/test-run-watch-run-duration(4) -
parallel/test-watch-mode-files_watcher(3) -
test-runner/test-run-watch-repeatedly(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-net-autoselectfamily(2) -
parallel/test-runner-run(2) -
pummel/test-repl-paste-big-data(2) -
sequential/test-debugger-pid(2) -
sequential/test-performance-eventloopdelay(2) -
test-runner/test-output-test-runner-watch-spec(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 the linked CI job range and reports/2026-04-25.md, then inspect the listed Jenkins failures and recurring Node.js tests. Use the Progress checklist to track investigation; done means the recurring failures are addressed and the affected pull requests no longer fail for these causes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100