[
https://issues.apache.org/jira/browse/FLINK-33082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18121880#comment-18121880
]
Martijn Visser commented on FLINK-33082:
----------------------------------------
Again on release-1.20, nightly 2026-10-02 (e2e_1_cron_jdk17), this time Azure
Pipelines 16:
https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=79677&view=logs&j=64debf87-ecdb-5aef-788d-8720d341b5cb
{code}
We stopped hearing from agent Azure Pipelines 16. Verify the agent machine is
running and has a healthy network connection. Anything that terminates an agent
process, starves it for CPU, or blocks its network access can cause this error.
{code}
The last uploaded line is from 03:19, while the HA per-job cluster (hashmap,
async) test waited for the job submission. The logs were not uploaded.
> Azure Pipelines 4 is not responding on AZP
> ------------------------------------------
>
> Key: FLINK-33082
> URL: https://issues.apache.org/jira/browse/FLINK-33082
> Project: Flink
> Issue Type: Bug
> Components: Build System / CI
> Affects Versions: 1.17.2
> Reporter: Sergey Nuyanzin
> Priority: Major
> Labels: test-stability
>
> it impacts this build for 1.17
> [https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=53163&view=logs&s=9fca669f-5c5f-59c7-4118-e31c641064f0&j=6e8542d7-de38-5a33-4aca-458d6c87066d]
> {noformat}
> ##[error]We stopped hearing from agent Azure Pipelines 4. Verify the agent
> machine is running and has a healthy network connection. Anything that
> terminates an agent process, starves it for CPU, or blocks its network access
> can cause this error. For more information, see:
> https://go.microsoft.com/fwlink/?linkid=846610
> Agent: Azure Pipelines 4
> Started: Today at 4:59 AM
> Duration: 6h 24m 38s
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
