CI Reliability 2026-04-23
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/72775 to node-test-pull-request/72874 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-23.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-23 00:26 | 0 | 16 | 15 | 0 | 69 | 16.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-23.md to see failure details
Progress
-
wpt/test-wasm-jsapi(14) -
parallel/test-debugger-probe-json-preview(8) -
parallel/test-debugger-probe-global-option-order(7) -
parallel/test-debugger-probe-miss(7) -
sequential/test-watch-mode-restart-esm-loading-error(7) -
wpt/test-hr-time(6) -
parallel/test-debugger-probe-child-inspect-port-zero(5) -
parallel/test-debugger-probe-json(5) -
parallel/test-debugger-probe-text(5) -
parallel/test-debugger-probe-json-special-values(4) -
test-runner/test-run-watch-dependency-repeatedly(4) -
test-runner/test-run-watch-without-file(4) -
parallel/test-watch-mode-files_watcher(3) -
sequential/test-performance-eventloopdelay(3) -
test-runner/test-run-watch-run-duration(3) -
parallel/test-debugger-probe-text-special-values(2) -
parallel/test-http2-close-while-writing(2) -
pummel/test-repl-paste-big-data(2) -
test-runner/test-output-test-runner-watch-spec(2) -
test-runner/test-run-watch-cwd-isolation-none(2) -
test-runner/test-run-watch-repeatedly(2) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal: No rebase in progress?(3) -
Failed to trigger fanned build(2) -
sh: line 1: 404:: command not found(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-23.md and the linked node-test-pull-request jobs, then use the listed test names and build errors to identify recurring failures. Reproduce the affected jobs and trace each failure to its source; done means the listed recurring CI failures are resolved and the relevant jobs pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100