[Build failed] flink-ci.flink-master-mirror - flink-ci/flink-mirror:master - apache-flink - b464b331

              
Build #20260711.6 failed
flink-ci.flink-master-mirror
Ran for 3 hours
View results
Summary
Build pipeline flink-ci.flink-master-mirror
Finished Sat, Jul 11 2026 22:49:52 GMT+00:00
Reason Continuous integration
Details
e2e_2_cron_hadoop343
0 error(s), 0 warning(s)
e2e_4_cron_adaptive_scheduler
0 error(s), 0 warning(s)
e2e_1_cron_azure
0 error(s), 0 warning(s)
e2e_3_ci
0 error(s), 0 warning(s)
e2e_1_cron_adaptive_scheduler
0 error(s), 0 warning(s)
test_cron_jdk21
0 error(s), 0 warning(s)
e2e_1_cron_hadoop343
0 error(s), 0 warning(s)
cron_snapshot_deployment_maven
0 error(s), 0 warning(s)
e2e_4_cron_jdk11
0 error(s), 0 warning(s)
e2e_3_cron_adaptive_scheduler
0 error(s), 0 warning(s)
compile_ci
0 error(s), 0 warning(s)
e2e_4_cron_hadoop343
0 error(s), 0 warning(s)
e2e_2_cron_azure
0 error(s), 0 warning(s)
compile_cron_azure
0 error(s), 0 warning(s)
docs_404_check
0 error(s), 0 warning(s)
e2e_1_cron_jdk21
0 error(s), 0 warning(s)
e2e_4_cron_azure
0 error(s), 0 warning(s)
e2e_4_cron_jdk21
0 error(s), 0 warning(s)
e2e_3_cron_azure
0 error(s), 0 warning(s)
e2e_2_cron_adaptive_scheduler
0 error(s), 0 warning(s)
e2e_2_ci
0 error(s), 0 warning(s)
cron_snapshot_deployment_binary
0 error(s), 0 warning(s)
docs_404_check
0 error(s), 0 warning(s)
test_cron_adaptive_scheduler
0 error(s), 0 warning(s)
compile_cron_hadoop343
0 error(s), 0 warning(s)
test_cron_jdk11
0 error(s), 0 warning(s)
e2e_3_cron_hadoop343
0 error(s), 0 warning(s)
test_cron_hadoop343
0 error(s), 0 warning(s)
compile_cron_adaptive_scheduler
0 error(s), 0 warning(s)
e2e_4_ci
0 error(s), 0 warning(s)
test_cron_azure
0 error(s), 0 warning(s)
e2e_1_cron_jdk11
0 error(s), 0 warning(s)
build_wheels_on_Linux
0 error(s), 0 warning(s)
e2e_1_ci
0 error(s), 0 warning(s)
build_wheels_on_macos
0 error(s), 0 warning(s)
test_ci
2 error(s), 1 warning(s)
We stopped hearing from agent AlibabaCI001-agent01. 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
We stopped hearing from agent AlibabaCI007-agent01. 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
e2e_3_cron_jdk21
0 error(s), 0 warning(s)
e2e_2_cron_jdk11
0 error(s), 0 warning(s)
e2e_2_cron_jdk21
0 error(s), 0 warning(s)
e2e_3_cron_jdk11
0 error(s), 0 warning(s)
compile_cron_jdk11
0 error(s), 0 warning(s)
compile_cron_jdk21
0 error(s), 0 warning(s)
Test results
Failed 0
Passed 31678
Others 553
Total tests 32231
Total run duration 22 minutes
Commits
b464b331 [FLINK-40109] Verify Kerberos keytab logs after the YARN application is killed MartijnVisser
1a5f8687 [hotfix] Use `systemPropertyVariables` instead of `systemProperties` snuyanzin
We sent you this notification on behalf of [apache-flink]\apache-flink Team. View
Microsoft respects your privacy. Review our Online Services Privacy Statement.
One Microsoft Way, Redmond, WA, USA 98052.
Sent from Azure DevOps

Reply via email to