CI Reliability 2025-06-20
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/67449 to node-test-pull-request/67545 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-06-20.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-06-20 00:12 | 3 | 0 | 18 | 0 | 79 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-06-20.md to see failure details
Progress
-
parallel/test-buffer-tostring-range(17) -
parallel/test-config-file(16) -
pummel/test-string-decoder-large-buffer(16) -
parallel/test-fs-watch-recursive-delete(11) -
parallel/test-fs-write-buffer-large(11) -
pummel/test-buffer-large-size-buffer-alloc-unsafe(10) -
pummel/test-buffer-large-size-buffer-write(8) -
pummel/test-buffer-large-size-buffer-alloc-unsafe-slow(7) -
pummel/test-buffer-large-size-slowbuffer(6) -
parallel/test-fs-write-file-invalid-path(4) -
es-module/test-vm-contextified-script-leak(3) -
parallel/test-stream-readable-to-web(3) -
pummel/test-buffer-large-size-buffer-alloc(3) -
sequential/test-performance-eventloopdelay(3) -
sequential/test-tls-session-timeout(3) -
wpt/test-streams(3) -
parallel/test-fs-write-negativeoffset(2) -
parallel/test-http2-close-while-writing(2) -
parallel/test-inspector-exit-worker-in-wait-for-connection(2) -
Build timed out (after 30 minutes). Marking the build as failed.(9) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Error fetching remote repo 'origin'(3) -
Failed to trigger node-test-commit(2) -
fatal: No rebase in progress?(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-20.md and the linked CI runs to inspect the failure details for the listed tests and infrastructure errors. Review the corresponding test names, then investigate the failures that recur across multiple pull requests. Done means the relevant entries are resolved and the progress checklist can be updated.
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
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100