CI Reliability 2025-09-29
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/69337 to node-test-pull-request/69434 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-09-29.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-09-29 00:12 | 0 | 3 | 3 | 4 | 90 | 3.13% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-09-29.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(6) -
Build timed out (after 30 minutes). Marking the build as failed.(3) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
Unexpected termination of the channel(2) -
fatal: No rebase in progress?(4) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(3) -
sequential/test-single-executable-application(45) -
sequential/test-single-executable-application-asset-keys(45) -
sequential/test-single-executable-application-asset-keys-empty(45) -
sequential/test-single-executable-application-assets(45) -
sequential/test-single-executable-application-assets-raw(45) -
sequential/test-single-executable-application-disable-experimental-sea-warning(45) -
sequential/test-single-executable-application-exec-argv(45) -
sequential/test-single-executable-application-exec-argv-empty(45) -
sequential/test-single-executable-application-exec-argv-extension-cli(45) -
sequential/test-single-executable-application-exec-argv-extension-env(45) -
sequential/test-single-executable-application-exec-argv-extension-none(45) -
sequential/test-single-executable-application-inspect(45) -
sequential/test-single-executable-application-inspect-in-sea-flags(45) -
sequential/test-single-executable-application-snapshot(45) -
sequential/test-single-executable-application-snapshot-and-code-cache(45) -
sequential/test-single-executable-application-snapshot-worker(45) -
sequential/test-single-executable-application-use-code-cache(45) -
parallel/test-runner-run-watch(32) -
client-proxy/test-https-proxy-request-invalid-char-in-url(12) -
parallel/test-without-async-context-frame(10) -
sequential/test-perf-hooks(9) -
parallel/test-runner-watch-mode-kill-signal(8) -
parallel/test-http2-close-while-writing(6) -
parallel/test-fs-promises-watch-iterator(4) -
parallel/test-quic-test-client(3) -
wasi/test-wasi-pthread(3) -
wpt/test-hr-time(3) -
parallel/test-repl-paste-big-data(2) -
parallel/test-runner-mock-timers-scheduler(2) -
parallel/test-runner-run(2) -
sequential/test-performance-eventloopdelay(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-09-29.md and the linked node-test-pull-request builds; the issue was generated with ncu-ci walk pr --stats=true --markdown reports/2025-09-29.md. Trace the listed timeout, channel, and test failures to their causes, with completion shown by the repeated CI failures being addressed and the report no longer showing them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100