[FLINK-19654] Improve the execution time of PyFlink end-to-end tests

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.12.0
• Fix Version/s: 1.12.0
• Component/s: API / Python, Tests
• Labels: auto-deprioritized-major auto-unassigned pull-request-available
• Assignee: Huang Xingbo
• Reporter: Dian Fu
• Created: 15/Oct/20 05:13
• Updated: 22/Jun/21 08:41
• Resolved: 22/Jun/21 08:40

Description

Thanks for the sharing from rmetzger, currently the test duration for PyFlink end-to-end test is as following:

test case	average execution-time	maximum execution-time
PyFlink Table end-to-end test	1340s	1877s
PyFlink DataStream end-to-end test	387s	575s
Kubernetes PyFlink application test	606s	694s

We need to investigate how to improve them to reduce the execution time.

Issue Links

• relates to: FLINK-19549 [CI] ##[error]The job running on agent Azure Pipelines 5 ran longer than the maximum time of 260 minutes.
• links to: GitHub Pull Request #13652
• links to: GitHub Pull Request #13659
• links to: GitHub Pull Request #13736