Hi Sunny, We are just getting started with Jenkins and may have to fine tune the CI setup a bit. Apart from a few unreliable Flink tests, Travis has its own issues because resources tend to be heavily limited there.
Feel free to contact one of the shepherds for the component: https://cwiki.apache.org/confluence/display/FLINK/Components+and+Shepherds Cheers, Max On Mon, Aug 15, 2016 at 11:33 PM, Sunny T <tsunny....@gmail.com> wrote: > Hi, > > Thanks for the information. > > Any idea whom I should contact to have a look at the pull request and get it > approved? > > > > Thanks, > Sunny T > > On Mon, Aug 15, 2016 at 12:07 PM Ivan Mushketyk <Ivan Mushketyk > wrote: >> >> Hi, >> >> Some Flink tests are flaky and fail on some platforms, so failures may >> have >> nothing to do with your changes. >> Since your build passes on most platforms, I would assume that the code is >> fine, but it is up to someone more experienced in Flink to decide. >> Flink community is working towards improving this, but right now we have >> to >> deal with it. >> >> Best regards, >> Ivan. >> >> On Mon, 15 Aug 2016 at 17:41 Sunny T tsunny....@gmail.com> wrote: >> >> > Hi, >> > >> > I created a pull request for FLINK-4309 last night. Here is the pull >> > request: https://github.com/apache/flink/pull/2371. >> > >> > The jenkins and Travis CI are failing. But the Travis CI passed on my >> > forked repository. >> > >> > Can anyone help me understand what is wrong here? >> > >> > Thanks, >> > Sunny >> > > >
