CI Reliability 2026-03-29
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/72074 to node-test-pull-request/72168 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-03-29.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-03-29 00:19 | 10 | 9 | 3 | 32 | 46 | 15.52% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-03-29.md to see failure details
Progress
-
sequential/test-debugger-pid(17) -
client-proxy/test-https-proxy-request-proxy-failure-404(2) -
parallel/test-debugger-heap-profiler(2) -
parallel/test-http-allow-content-length-304(2) -
parallel/test-http-client-parse-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 reports/2026-03-29.md and the linked CI runs for the five listed test failures. Investigate each failure in the corresponding Node.js test, then rerun the affected CI tests. Done means the listed failures no longer reproduce and the progress items can be checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100