CI Reliability 2026-03-30
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/72142 to node-test-pull-request/72240 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-03-30.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-03-30 00:19 | 5 | 8 | 0 | 28 | 59 | 11.94% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-03-30.md to see failure details
Progress
-
Failed to trigger node-test-commit(10) -
fatal: No rebase in progress?(3) -
Failed to trigger fanned build(2) -
sequential/test-debugger-pid(7) -
wpt/test-webcrypto(3) -
client-proxy/test-http-set-global-proxy-from-env-fetch(2) -
parallel/test-http-client-aborted-event(2) -
parallel/test-http-client-race-2(2) -
parallel/test-http-zero-length-write(2) -
parallel/test-net-server-keepalive(2) -
sequential/test-watch-mode-restart-esm-loading-error(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 the linked CI job range and the failure details in reports/2026-03-30.md. Review the listed progress items, including the trigger failures and named Node.js tests, then use the report to identify recurring causes. Done means resolving the repeated failures and updating the progress checklist.
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
- Mostly clear
- Newbie friendliness
- 45/100