hulincup commented on PR #28853:
URL: https://github.com/apache/flink/pull/28853#issuecomment-5140879494
## Root cause of the CI failure identified
I downloaded the full Azure log and found the exact failure. It is **not**
related to this docs-only change.
**Failing module:** `flink-runtime-web` (the Angular web dashboard, not
`docs/`)
**Failing step:** `frontend-maven-plugin:npm (npm install)` → `npm ci` in
`flink-runtime-web/web-dashboard`
**Exact error:**
```
[INFO] Running 'npm ci ${npm.proxy}' in
/__w/2/s/flink-runtime-web/web-dashboard
[INFO] npm error code ECONNRESET
[INFO] npm error network aborted
[INFO] npm error network This is a problem related to network connectivity.
[INFO] npm error network In most cases you are behind a proxy or have bad
network settings.
```
This is an **infrastructure flake** — the Azure runner's `npm ci` was
aborted by a transient network reset (`ECONNRESET`) while fetching npm
packages. It has nothing to do with the 13 `.md` files this PR touches under
`docs/content/`.
The earlier `@flinkbot run azure` did not actually spawn a new build (the
bot kept referencing build 77606). Pushing an empty commit to retrigger a fresh
CI run.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
