[
https://issues.apache.org/jira/browse/FLINK-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302002#comment-15302002
]
ASF GitHub Bot commented on FLINK-2915:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/2027#issuecomment-221856876
Thanks for looking into this!
I think that increasing the test timeout will not solve the problem. In
fact, the CI system kills stalled tests after 5 minutes anyways, that would be
even before the 10 minutes timeout is met.
Looking at the commit history, I think that the test was already improved a
bit since the issue was opened. The problem may actually have been fixed
already.
> JobManagerProcessFailureBatchRecoveryITCase
> -------------------------------------------
>
> Key: FLINK-2915
> URL: https://issues.apache.org/jira/browse/FLINK-2915
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Reporter: Matthias J. Sax
> Assignee: Rekha Joshi
> Priority: Critical
> Labels: test-stability
>
> https://travis-ci.org/apache/flink/jobs/87193692
> {noformat}
> Failed tests:
> JobManagerProcessFailureBatchRecoveryITCase>AbstractJobManagerProcessFailureRecoveryITCase.testJobManagerProcessFailure:259
> JobManager did not start up within 291736881301 nanoseconds.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
