CI Reliability 2025-06-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/67614 to node-test-pull-request/67710 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-06-29.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-06-29 00:13 | 1 | 0 | 42 | 1 | 56 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-06-29.md to see failure details
Progress
-
pummel/test-string-decoder-large-buffer(15) -
parallel/test-buffer-tostring-range(11) -
parallel/test-config-file(7) -
parallel/test-stream-readable-to-web(5) -
sequential/test-tls-session-timeout(4) -
parallel/test-debugger-extract-function-name(3) -
parallel/test-worker-message-port-transfer-filehandle(3) -
parallel/test-worker-nearheaplimit-deadlock(3) -
pummel/test-buffer-large-size-buffer-alloc-unsafe(3) -
wpt/test-streams(3) -
parallel/test-inspector-connect-to-main-thread(2) -
sequential/test-performance-eventloopdelay(2) -
wpt/test-webcrypto(2) -
Build timed out (after 30 minutes). Marking the build as failed.(5) -
ERROR: Error fetching remote repo 'origin'(3)
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-29.md and the linked node-test-pull-request jobs 67614 through 67710. Review the listed failing tests, timeouts, and repository-fetch errors to identify which failures are actionable. Done means the reported CI failures have been addressed and the affected checks no longer fail repeatedly.
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