CI Reliability 2026-04-11
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/72519 to node-test-pull-request/72616 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-11.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-11 00:19 | 1 | 21 | 21 | 14 | 43 | 24.71% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-11.md to see failure details
Progress
-
Unexpected termination of the channel(4) -
Failed to trigger node-test-commit(2) -
fatal: No rebase in progress?(2) -
parallel/test-runner-output(7) -
wpt/test-wasm-jsapi(6) -
test-runner/test-run-watch-run-duration(5) -
client-proxy/test-https-proxy-request-invalid-char-in-url(3) -
parallel/test-debugger-heap-profiler(2) -
parallel/test-inspector-dom-storage(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
test-runner/test-run-watch-without-file(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-11.md and the linked node-test-pull-request runs, then use the listed failure names and counts to trace each recurring CI problem. Done means the relevant failures have been investigated and the corresponding progress items can be checked off without recurring failures.
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