CI Reliability 2025-06-14
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/67333 to node-test-pull-request/67431 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-06-14.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-06-14 00:11 | 0 | 2 | 36 | 5 | 57 | 2.11% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-06-14.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(8) -
ERROR: Error fetching remote repo 'origin'(2) -
Failed to trigger node-test-commit(3) -
fatal error: Killed signal terminated program cc1plus(2) -
parallel/test-buffer-tostring-range(10) -
sequential/test-performance-eventloopdelay(7) -
parallel/test-stream-readable-to-web(5) -
sequential/test-tls-session-timeout(4) -
parallel/test-config-file(3) -
parallel/test-without-async-context-frame(2) -
wpt/test-webcrypto(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-14.md and the ncu-ci walk pr --stats=true --markdown command, then inspect the linked Jenkins runs for the recurring failures listed in the issue. Done means identifying and addressing the reported CI failures and confirming that the affected jobs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100