CI Reliability 2026-04-13
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/72562 to node-test-pull-request/72655 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-13.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-13 00:21 | 0 | 23 | 14 | 14 | 49 | 26.74% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-13.md to see failure details
Progress
-
Unexpected termination of the channel(3) -
fatal: No rebase in progress?(3) -
Failed to trigger node-test-commit(2) -
parallel/test-runner-output(6) -
test-runner/test-run-watch-run-duration(4) -
wpt/test-wasm-jsapi(4) -
test-runner/test-run-watch-without-file(3) -
wpt/test-hr-time(3) -
parallel/test-net-connect-memleak(2) -
sequential/test-performance-eventloopdelay(2) -
test-runner/test-run-watch-dependency-repeatedly(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-13.md and the linked node-test-pull-request jobs to inspect the failure details. Work through the unchecked failure groups, including the named test files and CI errors, then verify the affected failures no longer recur in CI and the reliability report can be marked complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, nodejs, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100