CI Reliability 2025-10-01
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/69382 to node-test-pull-request/69480 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-01.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-10-01 00:13 | 3 | 0 | 1 | 6 | 90 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-10-01.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(3) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
Unexpected termination of the channel(2) -
fatal: No rebase in progress?(3) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(2) -
sequential/test-single-executable-application(42) -
sequential/test-single-executable-application-asset-keys(42) -
sequential/test-single-executable-application-asset-keys-empty(42) -
sequential/test-single-executable-application-assets(42) -
sequential/test-single-executable-application-assets-raw(42) -
sequential/test-single-executable-application-disable-experimental-sea-warning(42) -
sequential/test-single-executable-application-exec-argv(42) -
sequential/test-single-executable-application-exec-argv-empty(42) -
sequential/test-single-executable-application-exec-argv-extension-cli(42) -
sequential/test-single-executable-application-exec-argv-extension-env(42) -
sequential/test-single-executable-application-exec-argv-extension-none(42) -
sequential/test-single-executable-application-inspect(42) -
sequential/test-single-executable-application-inspect-in-sea-flags(42) -
sequential/test-single-executable-application-snapshot(42) -
sequential/test-single-executable-application-snapshot-and-code-cache(42) -
sequential/test-single-executable-application-snapshot-worker(42) -
sequential/test-single-executable-application-use-code-cache(42) -
parallel/test-runner-run-watch(35) -
client-proxy/test-https-proxy-request-invalid-char-in-url(18) -
sequential/test-perf-hooks(12) -
parallel/test-runner-watch-mode-kill-signal(10) -
parallel/test-http2-close-while-writing(8) -
parallel/test-without-async-context-frame(8) -
parallel/test-quic-test-client(7) -
parallel/test-fs-promises-watch-iterator(4) -
wasi/test-wasi-pthread(3) -
wpt/test-hr-time(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-01.md linked from the issue and inspect the referenced node-test-pull-request builds, focusing on the repeated timeout, termination, rebase, reporting, and test failures. Done means the listed CI failure patterns have been investigated and addressed so subsequent runs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- ci-cd, devops, testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100