[
https://issues.apache.org/jira/browse/FLINK-34202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819183#comment-17819183
]
Matthias Pohl edited comment on FLINK-34202 at 2/21/24 10:57 AM:
-----------------------------------------------------------------
That still leaves the question open why we don't see this in other Alibaba VMs.
About the runner configuration: As far as I remember, there are 5 agents set up
per VM right now. This can be configured in the Azure Pipeline pool
configuration where you can enable/disable each agent individually.
was (Author: mapohl):
That still leaves the question open why we don't see this in other Alibaba VMs.
As far as I remember, there are 5 agents set up per VM right now. This can be
configured in the Azure Pipeline pool configuration where you can
enable/disable each agent individually.
> 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
> Attachments: Screenshot 2024-02-21 at 09.45.18.png
>
>
> [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)
