CI Reliability 2025-09-28
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/69305 to node-test-pull-request/69400 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-09-28.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-09-28 00:12 | 0 | 11 | 13 | 4 | 72 | 11.46% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-09-28.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(8) -
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) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(3) -
fatal: No rebase in progress?(2) -
sequential/test-single-executable-application(30) -
sequential/test-single-executable-application-asset-keys(30) -
sequential/test-single-executable-application-asset-keys-empty(30) -
sequential/test-single-executable-application-assets(30) -
sequential/test-single-executable-application-assets-raw(30) -
sequential/test-single-executable-application-disable-experimental-sea-warning(30) -
sequential/test-single-executable-application-exec-argv(30) -
sequential/test-single-executable-application-exec-argv-empty(30) -
sequential/test-single-executable-application-exec-argv-extension-cli(30) -
sequential/test-single-executable-application-exec-argv-extension-env(30) -
sequential/test-single-executable-application-exec-argv-extension-none(30) -
sequential/test-single-executable-application-inspect(30) -
sequential/test-single-executable-application-inspect-in-sea-flags(30) -
sequential/test-single-executable-application-snapshot(30) -
sequential/test-single-executable-application-snapshot-and-code-cache(30) -
sequential/test-single-executable-application-snapshot-worker(30) -
sequential/test-single-executable-application-use-code-cache(30) -
parallel/test-runner-run-watch(20) -
client-proxy/test-https-proxy-request-invalid-char-in-url(8) -
parallel/test-without-async-context-frame(8) -
sequential/test-perf-hooks(8) -
parallel/test-runner-watch-mode-kill-signal(7) -
parallel/test-http2-close-while-writing(5) -
parallel/test-fs-promises-watch-iterator(4) -
sequential/test-performance-eventloopdelay(3) -
parallel/test-repl-paste-big-data(2) -
parallel/test-runner-run(2) -
wasi/test-wasi-pthread(2) -
wpt/test-hr-time(2) -
wpt/test-streams(2) -
wpt/test-webcrypto(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-28.md and the linked node-test-pull-request builds, using the listed failure messages and test names to group the failures. Check the ncu-ci command shown in the issue and investigate the affected Jenkins jobs. Done means the listed recurring failures have been addressed and the CI reliability report no longer shows them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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