flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-1077) Flakey test CliFrontendPackageProgramTest
Date Sun, 21 Sep 2014 18:31:33 GMT

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

Stephan Ewen commented on FLINK-1077:
-------------------------------------

I have not seen this error lately, so I assume it is not an issue any more.

> Flakey test CliFrontendPackageProgramTest
> -----------------------------------------
>
>                 Key: FLINK-1077
>                 URL: https://issues.apache.org/jira/browse/FLINK-1077
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Stephan Ewen
>            Assignee: Timo Walther
>
> Test is error is CliFrontendPackageProgramTest # testPlanWithExternalClass()
> The error occurs in my recent travis builds one in 10 times or so.
> The following stack trace describes the error:
> {code}
> java.lang.AssertionError
>  at org.junit.Assert.fail(Assert.java:86)
>  at org.junit.Assert.assertTrue(Assert.java:41)
>  at org.junit.Assert.assertTrue(Assert.java:52)
>  at org.apache.flink.client.CliFrontendPackageProgramTest$1.loadClass(CliFrontendPackageProgramTest.java:249)
> {code}
> Is it possible that race conditions cause the classloader to be used for different classes
as well? In any case, the test should change the assertion to assertEquals, such that the
expected name is part of the error message (helps debugging what went wrong).



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

Mime
View raw message