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

Till Rohrmann commented on FLINK-8138:
--------------------------------------

Another instance: https://api.travis-ci.org/v3/job/344892913/log.txt

> Race in TaskAsyncCallTest leads to test time out
> ------------------------------------------------
>
>                 Key: FLINK-8138
>                 URL: https://issues.apache.org/jira/browse/FLINK-8138
>             Project: Flink
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 1.5.0
>            Reporter: Ufuk Celebi
>            Priority: Critical
>              Labels: test-stability
>             Fix For: 1.5.0
>
>         Attachments: log.txt
>
>
> {{TaskAsyncCallTest#testSetsUserCodeClassLoader}} times out with a stack 
> trace on Travis on a personal branch with unrelated changes on top of 1.4.0 
> RC 0.
> I've attached the Travis output to this issue. The main thread is stuck in
> {code}
> "main" #1 prio=5 os_prio=0 tid=0x00007ff59000a000 nid=0xb9b in Object.wait() 
> [0x00007ff598965000]
>    java.lang.Thread.State: WAITING (on object monitor)
>       at java.lang.Object.wait(Native Method)
>       - waiting on <0x00000000833994c8> (a java.lang.Object)
>       at java.lang.Object.wait(Object.java:502)
>       at 
> org.apache.flink.core.testutils.OneShotLatch.await(OneShotLatch.java:56)
>       - locked <0x00000000833994c8> (a java.lang.Object)
>       at 
> org.apache.flink.runtime.taskmanager.TaskAsyncCallTest.testSetsUserCodeClassLoader(TaskAsyncCallTest.java:201)
> {code}
> There are no other Flink related threads alive.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to