CI Reliability 2025-07-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/67860 to node-test-pull-request/67940 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-07-16.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-07-16 00:12 | 16 | 1 | 25 | 1 | 57 | 1.20% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-07-16.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(8) -
Build timed out (after 60 minutes). Marking the build as failed.(3) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Error fetching remote repo 'origin'(3) -
fatal: No rebase in progress?(6) -
Failed to trigger node-test-commit(5) -
es-module/test-esm-loader-chaining(5) -
es-module/test-esm-loader-event-loop(5) -
es-module/test-esm-loader-not-found(5) -
parallel/test-string-decoder(5) -
es-module/test-vm-contextified-script-leak(4) -
parallel/test-inspector-network-fetch(4) -
pummel/test-string-decoder-large-buffer(4) -
sequential/test-debugger-invalid-args(4) -
sequential/test-performance-eventloopdelay(4) -
wpt/test-streams(4) -
parallel/test-runner-watch-mode-kill-signal(3) -
parallel/test-worker-nearheaplimit-deadlock(3) -
es-module/test-esm-loader-hooks(2) -
parallel/test-buffer-tostring-range(2) -
parallel/test-process-threadCpuUsage-worker-threads(2) -
parallel/test-runner-run-watch(2) -
parallel/test-url-parse-invalid-input(2) -
parallel/test-v8-coverage(2) -
parallel/test-worker-message-port-transfer-filehandle(2) -
sequential/test-child-process-pass-fd(2) -
sequential/test-tls-session-timeout(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-07-16.md and the linked node-test-pull-request builds to group the repeated timeout, repository, trigger, and test failures. Compare the listed failures with their CI logs; done means the recurring failures have an identified resolution and the affected checks no longer recur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, devops, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100