[
https://issues.apache.org/jira/browse/FLINK-17945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125477#comment-17125477
]
Dian Fu edited comment on FLINK-17945 at 6/4/20, 2:21 AM:
----------------------------------------------------------
master: 19bbd6dbb4388645216201002e143833078f9bc1
release-1.11: fb3fc1ef82df6b73174c5aff28d54ab4eb96b094
release-1.10: dddd0f0e6341f0da053f2c1ace05b7b4fad527a2
release-1.9: e571b64032ceabab83c852ed7ed8a5292e2c5e85
was (Author: dian.fu):
master: 19bbd6dbb4388645216201002e143833078f9bc1
release-1.11: fb3fc1ef82df6b73174c5aff28d54ab4eb96b094
release-1.10: dddd0f0e6341f0da053f2c1ace05b7b4fad527a2
> Improve error reporting of Python CI tests
> ------------------------------------------
>
> Key: FLINK-17945
> URL: https://issues.apache.org/jira/browse/FLINK-17945
> Project: Flink
> Issue Type: Improvement
> Components: API / Python, Tests
> Affects Versions: 1.10.0, 1.11.0
> Reporter: Robert Metzger
> Assignee: Dian Fu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0, 1.10.2
>
>
> While working on some changes, I noticed that the error reporting of the
> Python tests is sometimes not very detailed.
> Example:
> {code}
> > self._j_elasticsearch = gateway.jvm.Elasticsearch()
> E TypeError: 'JavaPackage' object is not callable
> {code}
> https://dev.azure.com/rmetzger/Flink/_build/results?buildId=8081&view=logs&j=584fa981-f71a-5840-1c49-f800c954fe4b&t=532bf1f8-8c75-59c3-eaad-8c773769bc3a
> The probably root cause is that required JAR files are missing. It would be
> nice if the tests would show the underlying (java)Flink error / Flink logs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
