[
https://issues.apache.org/jira/browse/FLINK-15778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094946#comment-17094946
]
Jiangjie Qin commented on FLINK-15778:
--------------------------------------
>From the log it is hard to tell what happened. Some guess would be the broker
>start hit an exception and exited. This could be caused by issues such as the
>binding port is already taken.
To know the exact cause of the failure, we need to look at the broker log. The
broker should print the log to stdout by default, but for some reason the
broker log was not available in the testing log. I saw some Confluent schema
registry log printed to the testing log in other tests, but the broker logs are
somehow missing. [~rmetzger] do you happen to know what might cause the log
missing?
> SQL Client end-to-end test for Kafka 0.10 nightly run hung on travis
> --------------------------------------------------------------------
>
> Key: FLINK-15778
> URL: https://issues.apache.org/jira/browse/FLINK-15778
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka, Table SQL / Client
> Affects Versions: 1.10.0, 1.11.0
> Reporter: Yu Li
> Priority: Critical
> Labels: test-stability
> Fix For: 1.10.1, 1.11.0
>
>
> The "SQL Client end-to-end test for Kafka 0.10" end-to-end test hung on
> travis:
> {noformat}
> Waiting for broker...
> Waiting for broker...
> The job exceeded the maximum time limit for jobs, and has been terminated.
> {noformat}
> https://api.travis-ci.org/v3/job/642477196/log.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
