CI Reliability 2025-04-23
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/66317 to node-test-pull-request/66413 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-23.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-04-23 00:10 | 0 | 7 | 38 | 5 | 50 | 7.37% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-04-23.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(4) -
Failed to trigger node-test-commit(4) -
fatal error: Killed signal terminated program cc1plus(2) -
parallel/test-file-write-stream4(6) -
parallel/test-http2-options-max-headers-block-length(6) -
sequential/test-performance-eventloopdelay(4) -
parallel/test-debugger-break(3) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-http2-close-while-writing(2) -
parallel/test-runner-run-watch(2) -
sequential/test-tls-session-timeout(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 builds from node-test-pull-request/66317 through 66413 and the failure details in reports/2025-04-23.md. Review the listed timeout, trigger, compiler, and test failures, then use the Progress checklist to track each recurring failure until the report's failures are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100