CI Reliability 2026-04-14
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/72577 to node-test-pull-request/72674 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-14.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-14 00:24 | 0 | 23 | 15 | 14 | 48 | 26.74% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-14.md to see failure details
Progress
-
fatal: No rebase in progress?(3) -
Failed to trigger node-test-commit(2) -
parallel/test-runner-output(4) -
test-runner/test-run-watch-run-duration(4) -
test-runner/test-run-watch-without-file(4) -
wpt/test-wasm-jsapi(4) -
parallel/test-net-connect-memleak(2) -
sequential/test-fs-watch(2) -
sequential/test-performance-eventloopdelay(2) -
test-runner/test-run-watch-dependency-repeatedly(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-14.md and the linked node-test-pull-request builds 72577–72674. Review the failure details for the checked-list items, beginning with one repeated failure, and use the corresponding CI jobs to reproduce it. Done means the identified failures are fixed and the checklist items no longer recur across PRs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100