CI Reliability 2025-10-04
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/69430 to node-test-pull-request/69528 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-04.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-10-04 00:10 | 0 | 4 | 16 | 4 | 76 | 4.17% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-10-04.md to see failure details
Progress
-
Unexpected termination of the channel(9) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(3) -
fatal: detected dubious ownership in repository at 'C:/workspace/node-test-binary-windows-js-suites/build'(3) -
parallel/test-runner-run-watch(27) -
sequential/test-single-executable-application(21) -
sequential/test-single-executable-application-asset-keys(21) -
sequential/test-single-executable-application-asset-keys-empty(21) -
sequential/test-single-executable-application-assets(21) -
sequential/test-single-executable-application-assets-raw(21) -
sequential/test-single-executable-application-disable-experimental-sea-warning(21) -
sequential/test-single-executable-application-exec-argv(21) -
sequential/test-single-executable-application-exec-argv-empty(21) -
sequential/test-single-executable-application-exec-argv-extension-cli(21) -
sequential/test-single-executable-application-exec-argv-extension-env(21) -
sequential/test-single-executable-application-exec-argv-extension-none(21) -
sequential/test-single-executable-application-inspect(21) -
sequential/test-single-executable-application-inspect-in-sea-flags(21) -
sequential/test-single-executable-application-snapshot(21) -
sequential/test-single-executable-application-snapshot-and-code-cache(21) -
sequential/test-single-executable-application-snapshot-worker(21) -
sequential/test-single-executable-application-use-code-cache(21) -
client-proxy/test-https-proxy-request-invalid-char-in-url(15) -
parallel/test-runner-watch-mode-kill-signal(11) -
parallel/test-quic-test-client(9) -
sequential/test-perf-hooks(8) -
parallel/test-without-async-context-frame(6) -
parallel/test-http2-close-while-writing(5) -
parallel/test-fs-promises-watch-iterator(3) -
wpt/test-hr-time(3) -
sequential/test-gc-http-client(2) -
wpt/test-streams(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-04.md and the linked node-test-pull-request builds; the issue was generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-04.md. Review the listed failure groups, including the runner, executable-application, Windows ownership, and timeout failures; done means the selected failures are resolved and the corresponding checklist items can be checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, 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