CI Reliability 2025-10-06
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/69475 to node-test-pull-request/69574 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-06.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-10-06 00:11 | 0 | 4 | 28 | 2 | 66 | 4.08% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-10-06.md to see failure details
Progress
-
Unexpected termination of the channel(8) -
Build timed out (after 30 minutes). Marking the build as failed.(5) -
fatal: detected dubious ownership in repository at 'C:/workspace/node-test-binary-windows-js-suites/build'(5) -
Failed to trigger node-test-commit(3) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(2) -
parallel/test-runner-run-watch(18) -
parallel/test-without-async-context-frame(9) -
client-proxy/test-https-proxy-request-invalid-char-in-url(8) -
parallel/test-runner-watch-mode-kill-signal(7) -
parallel/test-quic-test-client(5) -
parallel/test-runner-run(4) -
sequential/test-perf-hooks(4) -
wpt/test-hr-time(3) -
wpt/test-streams(3) -
parallel/test-http2-close-while-writing(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
sequential/test-gc-http-client(2) -
sequential/test-worker-prof(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-06.md and the linked node-test-pull-request builds; the report was generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-06.md. Review the listed failure patterns and test names, then address the failures and update the Progress checklist as they are resolved.
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
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100