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

Huang Xingbo commented on FLINK-23493:
--------------------------------------

Let me synchronize the results of the survey.

1. The reason for hang is that the process started on the java side is waiting 
for the python side to start the client to connect to it, but I don’t know why 
the python side has not been able to connect to it. In fact, if there is an 
error, python process will throw the error message and exit. So from the 
perspective of the phenomenon, we can know there is no error in starting python 
process. On the other hand, in lack of info logs, I haven't discover the root 
cause of Python side can't connect to java side.

2. Another phenomenon is that all the hangs tests are in `cron_azure`. Compared 
with the stages `cron_hadoop241`, `cron_hadoop313`, and `cron_scala212` which 
will also test python related tests, `cron_azure` will use Azure vm to test. 
But `cron_hadoop241`, `cron_hadoop313`, and `cron_scala212` will use the 
Alibaba Cloud host to test directly. 

3. From https://issues.apache.org/jira/browse/FLINK-22856, we update the vm 
version from `ubuntu-16` to `ubuntu-20`, and I'm not sure whether it is 
relevant to this.

> python tests hang on Azure
> --------------------------
>
>                 Key: FLINK-23493
>                 URL: https://issues.apache.org/jira/browse/FLINK-23493
>             Project: Flink
>          Issue Type: Bug
>          Components: API / Python
>    Affects Versions: 1.14.0, 1.13.1, 1.12.4
>            Reporter: Dawid Wysakowicz
>            Assignee: Huang Xingbo
>            Priority: Blocker
>              Labels: test-stability
>             Fix For: 1.14.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=20898&view=logs&j=821b528f-1eed-5598-a3b4-7f748b13f261&t=4fad9527-b9a5-5015-1b70-8356e5c91490&l=22829



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to