CI Reliability 2026-04-22
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/72743 to node-test-pull-request/72838 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-22.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-22 00:21 | 0 | 18 | 12 | 0 | 70 | 18.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-22.md to see failure details
Progress
-
wpt/test-wasm-jsapi(14) -
parallel/test-debugger-probe-json-preview(7) -
parallel/test-debugger-probe-global-option-order(6) -
wpt/test-hr-time(6) -
parallel/test-debugger-probe-miss(5) -
sequential/test-watch-mode-restart-esm-loading-error(5) -
parallel/test-debugger-probe-child-inspect-port-zero(4) -
test-runner/test-run-watch-dependency-repeatedly(4) -
wpt/test-streams(4) -
- /home/iojs/build/workspace/node-test-linter/lib/internal/webstreams/util.js(3) -
parallel/test-debugger-probe-text(3) -
test-runner/test-run-watch-cwd-isolation-none(3) -
parallel/test-debugger-probe-json(2) -
parallel/test-debugger-probe-json-special-values(2) -
parallel/test-debugger-probe-text-special-values(2) -
parallel/test-watch-mode-files_watcher(2) -
sequential/test-performance-eventloopdelay(2) -
test-runner/test-output-test-runner-watch-spec(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-22.md, linked from the issue, and compare it with the listed failing tests and CI errors. Investigate the failures beginning with the highest-count entries such as wpt/test-wasm-jsapi and the debugger probe tests. Done means the reported CI failures are addressed and the affected checks can pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, 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