CI Reliability 2026-04-12
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/72542 to node-test-pull-request/72637 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-12.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-12 00:21 | 0 | 22 | 19 | 19 | 40 | 27.16% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-12.md to see failure details
Progress
-
Unexpected termination of the channel(3) -
Failed to trigger node-test-commit(2) -
fatal: No rebase in progress?(2) -
parallel/test-runner-output(6) -
test-runner/test-run-watch-run-duration(4) -
wpt/test-wasm-jsapi(4) -
client-proxy/test-https-proxy-request-invalid-char-in-url(3) -
sequential/test-performance-eventloopdelay(2) -
test-runner/test-run-watch-without-file(2) -
wpt/test-hr-time(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-12.md and the linked node-test-pull-request jobs, using the generated ncu-ci walk pr --stats=true --markdown command as context. Review the listed failures, beginning with the repeated channel, trigger, rebase, test-runner, WPT, proxy, and performance failures. Done means the reported CI failures are investigated and the corresponding progress items can be checked off.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100