[
https://issues.apache.org/jira/browse/FLINK-34202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818374#comment-17818374
]
Matthias Pohl commented on FLINK-34202:
---------------------------------------
Thanks for looking into it, everyone. We use random feature selection in other
places as well (e.g. with [buffer
debloating|https://github.com/apache/flink/blob/c8f27c25e8726360bd09fd21fa8e908c40376881/flink-runtime/src/test/java/org/apache/flink/runtime/testutils/MiniClusterResource.java#L256]).
So, generally, I'm not against it but leave the judgement to you who are more
familiar with the Python module. On the other hand, [~hxb] concludes that
there's something wrong with the Alibaba001 VM. Therefore, we might want to
check that VM fix the actual issue there rather than working around it in the
Python tests. The actual cause might lead to problems in other tests as well.
WDYT?
> python tests take suspiciously long in some of the cases
> --------------------------------------------------------
>
> Key: FLINK-34202
> URL: https://issues.apache.org/jira/browse/FLINK-34202
> Project: Flink
> Issue Type: Bug
> Components: API / Python
> Affects Versions: 1.17.2, 1.19.0, 1.18.1
> Reporter: Matthias Pohl
> Assignee: Xingbo Huang
> Priority: Critical
> Labels: pull-request-available, test-stability
>
> [This release-1.18
> build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56603&view=logs&j=3e4dd1a2-fe2f-5e5d-a581-48087e718d53&t=b4612f28-e3b5-5853-8a8b-610ae894217a]
> has the python stage running into a timeout without any obvious reason. The
> [python stage run for
> JDK17|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=56603&view=logs&j=b53e1644-5cb4-5a3b-5d48-f523f39bcf06]
> was also getting close to the 4h timeout.
> I'm creating this issue for documentation purposes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
