CI Reliability 2025-06-16
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/67374 to node-test-pull-request/67471 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-06-16.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-06-16 00:12 | 1 | 1 | 25 | 8 | 65 | 1.10% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-06-16.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(5) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal error: Killed signal terminated program cc1plus(4) -
Failed to trigger node-test-commit(2) -
sh: line 12: [: -gt: unary operator expected(2) -
parallel/test-buffer-tostring-range(10) -
sequential/test-performance-eventloopdelay(6) -
parallel/test-config-file(5) -
parallel/test-stream-readable-to-web(5) -
pummel/test-string-decoder-large-buffer(4) -
parallel/test-without-async-context-frame(3) -
pummel/test-buffer-large-size-buffer-write(3) -
parallel/test-worker-nearheaplimit-deadlock(2) -
pummel/test-buffer-large-size-buffer-alloc-unsafe(2) -
pummel/test-buffer-large-size-buffer-alloc-unsafe-slow(2) -
sequential/test-tls-session-timeout(2) -
wpt/test-streams(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/2025-06-16.md and the linked node-test-pull-request builds to investigate the repeated failures listed in the Progress section. Read the relevant CI job output and associated test names first; done means the recurring failures are addressed and the affected CI runs become reliable again.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100