Github user rekhajoshm closed the pull request at:
https://github.com/apache/flink/pull/2027
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rekhajoshm commented on the pull request:
https://github.com/apache/flink/pull/2027#issuecomment-222198043
Thanks @StephanEwen for review. Closing PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your pr
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/2027#issuecomment-221856995
I would vote to close the issue and pull request for now, and see if the
test is stable now.
---
If your project is set up for it, you can reply to this email and h
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 anyw
GitHub user rekhajoshm opened a pull request:
https://github.com/apache/flink/pull/2027
[FLINK-2915] Fix for JobManagerProcessFailureBatchRecoveryITCase Test
[FLINK-2915] Fix for JobManagerProcessFailureBatchRecoveryITCase Test
You can merge this pull request into a Git repository b
