[ 
https://issues.apache.org/jira/browse/FLINK-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601421#comment-15601421
 ] 

Robert Metzger commented on FLINK-4235:
---------------------------------------

It seems like this happened again

{code}
testDisposeSavepointWithCustomKvState(org.apache.flink.test.classloading.ClassLoaderITCase)
  Time elapsed: 100.018 sec  <<< ERROR!
java.util.concurrent.TimeoutException: Futures timed out after [7263142827 
nanoseconds]
        at scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:219)
        at 
scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:223)
        at scala.concurrent.Await$$anonfun$result$1.apply(package.scala:190)
        at 
scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:53)
        at scala.concurrent.Await$.result(package.scala:190)
        at scala.concurrent.Await.result(package.scala)
        at 
org.apache.flink.test.classloading.ClassLoaderITCase.testDisposeSavepointWithCustomKvState(ClassLoaderITCase.java:300)
{code}

https://s3.amazonaws.com/archive.travis-ci.org/jobs/169700823/log.txt

> ClassLoaderITCase.testDisposeSavepointWithCustomKvState timed out on Travis
> ---------------------------------------------------------------------------
>
>                 Key: FLINK-4235
>                 URL: https://issues.apache.org/jira/browse/FLINK-4235
>             Project: Flink
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 1.1.0
>            Reporter: Till Rohrmann
>            Assignee: Ufuk Celebi
>              Labels: test-stability
>             Fix For: 1.1.0
>
>
> The {{ClasLoaderITCase.testDisposeSavepointWithCustomKvState}} timed out on 
> Travis. A potential fix could be to increase the timeouts for this test. When 
> fixing this issue, then we should let the {{ClassLoaderITCase}} extend the 
> {{TestLogger}}.
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/145882668/log.txt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to