[
https://issues.apache.org/jira/browse/FLINK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14768989#comment-14768989
]
Stephan Ewen commented on FLINK-2670:
-------------------------------------
I added an extra test for the critical part (that I originally suspected to be
broken) in 31f63178df2f81682527ba3debf9027bde78149b
Other than that, I cannot see what we can do. Looks like a hiccup in the
environment that caused the JVM to get stuck in the native call that traverses
the stack and fills in the stack trace.
I would actually close this as "cannot reproduce"...
> Unstable CombineTaskTest
> ------------------------
>
> Key: FLINK-2670
> URL: https://issues.apache.org/jira/browse/FLINK-2670
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Reporter: Matthias J. Sax
> Assignee: Stephan Ewen
> Priority: Critical
> Labels: test-stability
>
> Fails with
> {noformat}
> ==============================================================================
> Maven produced no output for 300 seconds.
> ==============================================================================
> {noformat}
> https://travis-ci.org/apache/flink/jobs/80344487
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
