CI Reliability 2026-04-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/72829 to node-test-pull-request/72924 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-26.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-26 00:24 | 0 | 16 | 16 | 1 | 67 | 16.16% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-26.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) -
Failed to trigger fanned build(2) -
parallel/test-debugger-probe-json-preview(9) -
parallel/test-debugger-probe-child-inspect-port-zero(8) -
test-runner/test-run-watch-without-file(7) -
wpt/test-wasm-jsapi(7) -
parallel/test-debugger-probe-miss(6) -
wpt/test-hr-time(6) -
parallel/test-debugger-probe-json-special-values(5) -
parallel/test-debugger-probe-text(5) -
test-runner/test-run-watch-dependency-repeatedly(5) -
test-runner/test-run-watch-run-duration(5) -
parallel/test-debugger-probe-global-option-order(4) -
parallel/test-debugger-probe-json(4) -
parallel/test-process-finalization(4) -
parallel/test-sqlite-database-sync(4) -
sequential/test-watch-mode-restart-esm-loading-error(4) -
test-runner/test-run-watch-cwd-isolation-none(4) -
test-runner/test-run-watch-repeatedly(4) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-runner-run(2) -
pummel/test-repl-paste-big-data(2) -
sequential/test-debugger-pid(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 with reports/2026-04-26.md and the linked node-test-pull-request jobs to inspect the reported failure details. Reproduce the listed failures and trace their causes across the CI runs. Done means the failure categories are resolved or explained and affected PR jobs return successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100