CI Reliability 2025-07-04
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/67732 to node-test-pull-request/67828 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-07-04.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-07-04 00:11 | 0 | 0 | 30 | 1 | 69 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-07-04.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(9) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
Failed to trigger sub builds(2) -
fatal error: Killed signal terminated program cc1plus(2) -
parallel/test-runner-watch-mode-kill-signal(18) -
pummel/test-string-decoder-large-buffer(17) -
parallel/test-child-process-advanced-serialization-splitted-length-field(13) -
parallel/test-config-file(11) -
parallel/test-worker-message-port-transfer-filehandle(6) -
es-module/test-vm-contextified-script-leak(4) -
parallel/test-stream-readable-to-web(4) -
parallel/test-runner-run-watch(2) -
sequential/test-performance-eventloopdelay(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 node-test-pull-request Jenkins builds and the generated reports/2025-07-04.md report. Review the repeated failures listed in the issue, including the timeout messages and named Node.js tests, then run or inspect the relevant CI jobs. Done means the listed recurring failures are addressed and the CI jobs no longer fail repeatedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100