You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/09/24 10:40:00 UTC
[jira] [Updated] (FLINK-14185) AbstractServerTest failed on Travis
[ https://issues.apache.org/jira/browse/FLINK-14185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-14185:
-----------------------------------
Labels: pull-request-available (was: )
> AbstractServerTest failed on Travis
> -----------------------------------
>
> Key: FLINK-14185
> URL: https://issues.apache.org/jira/browse/FLINK-14185
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Reporter: Yingjie Cao
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
>
> AbstractServerTest failed on Travis. The Travis link is [https://api.travis-ci.org/v3/job/588761985/log.txt]. The error message is as follows.
> {code:java}
> 05:53:23.924 [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.113 s <<< FAILURE! - in org.apache.flink.queryablestate.network.AbstractServerTest
> 05:53:23.924 [ERROR] testPortRangeSuccess(org.apache.flink.queryablestate.network.AbstractServerTest) Time elapsed: 0.064 s <<< FAILURE!
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.apache.flink.queryablestate.network.AbstractServerTest.testPortRangeSuccess(AbstractServerTest.java:126)
> {code}
> The failure can be reproduced by running the test case multi times (until failure) locally.
> The failure reason is that the requestStats is shared by two instance of TestServer which relies on AutoCloseable interface for connection release. If one of the server has been shut down and the anther is not, the assertion in the close method can fail. To fix the problem, we can move the assertion out of the close method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)