[
https://issues.apache.org/jira/browse/FLINK-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17030623#comment-17030623
]
Stephan Ewen commented on FLINK-15921:
--------------------------------------
As a general comment: I personally thing that the "auto newest version"
dependencies management that some environments do (node, python, etc) is a
super bad idea. It invites build problems and security issues (like when a repo
for a common JS utility was taken over, maleware injected, released, and
millions of systems auto-updated to that newest version, pulling the malware).
> Travis-ci error: PYTHON exited with EXIT CODE: 143
> ---------------------------------------------------
>
> Key: FLINK-15921
> URL: https://issues.apache.org/jira/browse/FLINK-15921
> Project: Flink
> Issue Type: Test
> Components: Build System
> Affects Versions: 1.10.0, 1.11.0
> Reporter: sunjincheng
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, some Travis CI failures occur, such as: [1],[2]. The reason for
> the failure is that the python dependent `grpcio` released the latest version
> 1.27.0 [3] today, which resulted in the test cache not having the latest
> dependency, and the timeout of downloading in the repo. If the problem will
> be fixed after the first download when the network is in good condition. I am
> still watching the latest build [4]. If it fails for a long time, we will try
> to set a lower version of `grpcio` or optimize the current test case. I would
> like to watch for a while .
>
> What do you think?
>
> [1][https://travis-ci.org/apache/flink/builds/646250268]
> [2][https://travis-ci.org/apache/flink/jobs/646281060]
> [3] [https://pypi.org/project/grpcio/#files]
> [4][https://travis-ci.org/apache/flink/builds/646355253]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
