Gotcha. Thanks for paying attention to the Jenkins runs and bringing this up.
Sent from my iPhone > On Jul 9, 2016, at 10:43 PM, Lior Zeno <liorz...@gmail.com> wrote: > > Nope. The recent builds on Jenkins fail because of this test. >> On Jul 10, 2016 7:54 AM, "Mike Percy" <mpe...@apache.org> wrote: >> >> Only on Windows? >> >> Sent from my iPhone >> >>> On Jul 9, 2016, at 9:14 PM, Lior Zeno <liorz...@gmail.com> wrote: >>> >>> We have another one: >> org.apache.flume.client.avro.TestSpoolingFileLineReader.testDestinationExistsAndSameFileWindows >>> It throws IllegalStateException. >>>> On Jul 9, 2016 13:19, "Lior Zeno" <liorz...@gmail.com> wrote: >>>> >>>> I did, please see https://issues.apache.org/jira/browse/FLUME-2936. >>>> >>>>> On Sat, Jul 9, 2016 at 12:28 PM, Mike Percy <mpe...@apache.org> wrote: >>>>> >>>>> Hi Lior, >>>>> >>>>>> On Thu, Jun 23, 2016 at 8:58 AM, Lior Zeno <liorz...@gmail.com> >> wrote: >>>>>> >>>>>> 1. KafkaSource hangs in doStart at line 413: >>>>>> it = consumer.poll(1000).iterator(); >>>>>> I fixed that by simply changing HOST in KafkaSourceEmbeddedKafka to >>>>>> localhost. >>>>> >>>>> Could you submit a patch? >>>>> >>>>> 2. Out of memory exception. I fixed that by properly configuring >>>>> MAVEN_OPTS. >>>>> >>>>> Ah. Turns out I commented that out in my .bashrc a while back. Thanks >> for >>>>> the reminder! >>>>> >>>>> Mike >>>>> >>>>> >>>>>> >>>>>>> On Wed, Jun 22, 2016 at 9:25 AM, Mike Percy <mpe...@apache.org> >> wrote: >>>>>>> >>>>>>> The kafka source tests are extremely flaky. I haven't investigated >> it. >>>>>>> >>>>>>> Mike >>>>>>> >>>>>>> On Tue, Jun 21, 2016 at 9:23 PM, Lior Zeno <liorz...@gmail.com> >>>>> wrote: >>>>>>> >>>>>>>> Hi guys, >>>>>>>> I know that there are a few tests that are problematic, i.e. may >>>>> fail >>>>>>>> arbitrarily. Please reply here with all tests that are known to be >>>>>>> flaky. I >>>>>>>> will create a jira issue for fixing that. Obviously, we won't fix >>>>> all >>>>>>> tests >>>>>>>> in the project at this moment, but we can definitely fix that in the >>>>>>>> future. >>>>>>>> Currently, the goal I think we should achieve is stabilizing the >>>>> tests >>>>>>> and >>>>>>>> make sure that we don't have false build failures. >>>>>>>> >>>>>>>> Thanks >> >>
