CI Reliability 2025-10-09
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/69537 to node-test-pull-request/69628 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-09.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-10-09 00:10 | 4 | 0 | 31 | 3 | 62 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-10-09.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(3) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...(3) -
Failed to trigger node-test-commit(3) -
fatal: detected dubious ownership in repository at 'C:/workspace/node-test-binary-windows-js-suites/build'(2) -
parallel/test-without-async-context-frame(17) -
sequential/test-worker-prof(10) -
parallel/test-runner-run-watch(7) -
parallel/test-runner-watch-mode-kill-signal(7) -
client-proxy/test-https-proxy-request-invalid-char-in-url(6) -
sequential/test-perf-hooks(4) -
wpt/test-hr-time(4) -
parallel/test-runner-run(3) -
parallel/test-fs-watch-recursive-delete(2) -
parallel/test-quic-test-client(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
parallel/test-zlib-brotli-16GB(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-10-09.md and the linked node-test-pull-request jobs to inspect the listed timeout, connection, trigger, ownership, and test failures. Compare the failures across the reported PRs and determine which issues can be addressed; done means the recurring failures no longer affect the CI runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, infrastructure, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100