CI Reliability 2025-10-05
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/69465 to node-test-pull-request/69563 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-05.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-10-05 00:12 | 1 | 4 | 27 | 2 | 66 | 4.12% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-10-05.md to see failure details
Progress
-
Unexpected termination of the channel(8) -
Build timed out (after 30 minutes). Marking the build as failed.(4) -
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(24) -
client-proxy/test-https-proxy-request-invalid-char-in-url(10) -
parallel/test-without-async-context-frame(8) -
sequential/test-single-executable-application(8) -
sequential/test-single-executable-application-asset-keys(8) -
sequential/test-single-executable-application-asset-keys-empty(8) -
sequential/test-single-executable-application-assets(8) -
sequential/test-single-executable-application-assets-raw(8) -
sequential/test-single-executable-application-disable-experimental-sea-warning(8) -
sequential/test-single-executable-application-exec-argv(8) -
sequential/test-single-executable-application-exec-argv-empty(8) -
sequential/test-single-executable-application-exec-argv-extension-cli(8) -
sequential/test-single-executable-application-exec-argv-extension-env(8) -
sequential/test-single-executable-application-exec-argv-extension-none(8) -
sequential/test-single-executable-application-inspect(8) -
sequential/test-single-executable-application-inspect-in-sea-flags(8) -
sequential/test-single-executable-application-snapshot(8) -
sequential/test-single-executable-application-snapshot-and-code-cache(8) -
sequential/test-single-executable-application-snapshot-worker(8) -
sequential/test-single-executable-application-use-code-cache(8) -
parallel/test-quic-test-client(7) -
parallel/test-runner-watch-mode-kill-signal(7) -
parallel/test-http2-close-while-writing(5) -
sequential/test-perf-hooks(5) -
parallel/test-runner-run(4) -
sequential/test-gc-http-client(2) -
wpt/test-hr-time(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-05.md and the node-test-pull-request jobs 69465 through 69563, using the listed failure names to locate details. The issue covers many unrelated CI and test failures but does not identify a single entry point or define which failures should be addressed first, so completion criteria need clarification.
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
- 25/100