[
https://issues.apache.org/jira/browse/FLINK-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145539#comment-14145539
]
Stephan Ewen commented on FLINK-1077:
-------------------------------------
Seems like a Mockito hickup or so... The class loader is used for a totally
different mock.
I changed the code to allow other classes to be loaded, if the class name is
different from the expected name.
Fixed in 091f2bdfa5f30d42bd5b305558eba5a77563b277
> 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
> Fix For: 0.7-incubating
>
>
> 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)
