CI Reliability 2026-04-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/72843 to node-test-pull-request/72937 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-27.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-27 00:25 | 0 | 16 | 17 | 1 | 66 | 16.16% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-27.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Error fetching remote repo 'origin'(3) -
fatal: No rebase in progress?(6) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(2) -
parallel/test-debugger-probe-json-preview(7) -
wpt/test-hr-time(7) -
wpt/test-wasm-jsapi(7) -
parallel/test-debugger-probe-child-inspect-port-zero(6) -
parallel/test-debugger-probe-miss(6) -
parallel/test-sqlite-database-sync(6) -
test-runner/test-run-watch-without-file(6) -
parallel/test-debugger-probe-json-special-values(5) -
parallel/test-debugger-probe-text(5) -
parallel/test-process-finalization(5) -
sequential/test-debugger-pid(5) -
test-runner/test-run-watch-run-duration(5) -
parallel/test-debugger-probe-json(4) -
test-runner/test-run-watch-dependency-repeatedly(4) -
test-runner/test-run-watch-repeatedly(4) -
parallel/test-debugger-probe-global-option-order(3) -
sequential/test-watch-mode-restart-esm-loading-error(3) -
test-runner/test-run-watch-cwd-isolation-none(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-performance-eventloopdelay(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 by reading reports/2026-04-27.md, linked from the issue, and compare it with the listed failures from node-test-pull-request/72843 through 72937. The issue was generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-27.md; done means addressing the listed recurring CI failures and updating the progress checklist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, 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
- 35/100