[ 
https://issues.apache.org/jira/browse/FLINK-33082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124961#comment-18124961
 ] 

Martijn Visser commented on FLINK-33082:
----------------------------------------

Two more on the nightlies of 2026-10-08, release-1.20 
(e2e_2_cron_adaptive_scheduler, Azure Pipelines 8) and release-2.2 
(e2e_2_cron_jdk21, Azure Pipelines 9):
https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=79931&view=logs&j=fb37c667-81b7-5c22-dd91-846535e99a97
https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=79932&view=logs&j=dc1bf4ed-4646-531a-f094-e103042be549

{code}
We stopped hearing from agent Azure Pipelines 8. 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}

Both agents stopped uploading at 04:18-04:19 (one during the PyFlink e2e test, 
one between two e2e tests) and both jobs were abandoned at 04:30:58, so it 
looks like the agents went away together.

> 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, 1.20.6
>            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)

Reply via email to