Github user uce commented on the issue:
https://github.com/apache/flink/pull/2786
Closing in favour of #2933.
---
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
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2786
I think we should split up the tests that take so long into multiple files.
That should do the trick as well.
For example, the `EventTimeWindowCheckpointingITCase` can simply have an
Github user StefanRRichter commented on the issue:
https://github.com/apache/flink/pull/2786
+1 for increased timeout.
---
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
Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/2786
I think it's fine to increase the timeout.
---
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
