Github user rmetzger commented on the issue:
https://github.com/apache/flink/pull/3344
I agree that we have this issue again.
If you want faster feedback on your pull requests, I recommend setting up
travis for your flink fork. Then, every time you push to your repo, you'll
Github user addisonj commented on the issue:
https://github.com/apache/flink/pull/3344
Even with this in place, I am still regularly seeing timeouts on quite a
few PRs. In addition to the travis queue being backed up, its taking 12+ hours
to get feedback which is mostly just build
Github user rmetzger commented on the issue:
https://github.com/apache/flink/pull/3344
Since this is so easy to undo, I'll merge it for now. Lets see if people
start complaining
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user rmetzger commented on the issue:
https://github.com/apache/flink/pull/3344
Thank you for your feedback. The feedback seems to be clearer than expected.
If there are no objections within the next days, I'll merge the change.
---
If your project is set up for it, you
Github user uce commented on the issue:
https://github.com/apache/flink/pull/3344
I think that 10 minutes are actually quite an improvement. Currently, the
PR builds usually time out and we only see red crosses next to the PR
(including this one ;)). I would certainly try this setup.
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3344
Ten minutes allows for a significant number of new tests. Alternatively, we
did look at parallelizing the tests but there were some dependency issues and
the PR expired in review.
This
