[
https://issues.apache.org/jira/browse/FLINK-13746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932003#comment-16932003
]
Zijie Lu edited comment on FLINK-13746 at 9/18/19 8:38 AM:
-----------------------------------------------------------
In the function *check_logs_for_errors,* [Terror] is counted. Can we whitelist
it in this function?
was (Author: alfredlu):
Is [Terror] logged in the $FLINK_DIR/log? In the travis log, *Test exited with
exit code 0 but the logs contained errors, exceptions or non-empty .out files.*
And I don't found any function in the common.sh which is used to count
[Terror]. So where is [Terror] counted? I think it is counted in the *is
check_logs_for_errors* function.
> Elasticsearch (v2.3.5) sink end-to-end test fails on Travis
> -----------------------------------------------------------
>
> Key: FLINK-13746
> URL: https://issues.apache.org/jira/browse/FLINK-13746
> Project: Flink
> Issue Type: Bug
> Components: Connectors / ElasticSearch, Tests
> Affects Versions: 1.9.0, 1.10.0
> Reporter: Till Rohrmann
> Priority: Critical
> Labels: test-stability
> Fix For: 1.10.0, 1.9.1
>
>
> The {{Elasticsearch (v2.3.5) sink end-to-end test}} fails on Travis because
> it logs contain the following line:
> {code}
> INFO org.elasticsearch.plugins - [Terror] modules [], plugins [], sites []
> {code}
> Due to this, the error check is triggered.
> https://api.travis-ci.org/v3/job/572255901/log.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
