Did you miss the attachment?

On Fri, Jul 25, 2014 at 10:44 AM, David Corley <davidcor...@gmail.com>
wrote:

> Sure. Attaching here.
>
>
>
> On Fri, Jul 25, 2014 at 4:16 PM, Guozhang Wang <wangg...@gmail.com> wrote:
>
>> Could you get a thread dump when it hangs?
>>
>>
>> On Thu, Jul 24, 2014 at 11:01 PM, David Corley <davidcor...@gmail.com>
>> wrote:
>>
>> > Hey Gouzhang,
>> > Yes, I spotted that commit and had updated my working copy to that, but
>> the
>> > test is still hanging. If it's any help, the test looks like it's doing
>> > _something_  as the CPU usage ramps up significantly and stays there
>> until
>> > I kill the process.
>> > /Dave
>> >
>> >
>> > On Thu, Jul 24, 2014 at 4:10 PM, Guozhang Wang <wangg...@gmail.com>
>> wrote:
>> >
>> > > Hi Dave,
>> > >
>> > > KAFKA-1533 has just been committed targeting at this issue. Did your
>> > update
>> > > on trunk include this commit?
>> > >
>> > > commit ff05e9b3616a222e29a42f6e8fdf41945a417f41
>> > > Author: Guozhang Wang <guw...@linkedin.com>
>> > > Date:   Tue Jul 22 14:14:19 2014 -0700
>> > >
>> > > Guozhang
>> > >
>> > >     kafka-1533; transient unit test failure in
>> > ProducerFailureHandlingTest;
>> > > reviewed by Guozhang Wang; reviewed by Jun Rao
>> > >
>> > >
>> > >
>> > >
>> > > On Thu, Jul 24, 2014 at 5:52 AM, David Corley <davidcor...@gmail.com>
>> > > wrote:
>> > >
>> > > > Hey all,
>> > > > I'm trying my hand at writing some patches for open issues, but I'm
>> > > running
>> > > > into issues with running gradlew test.
>> > > > It hangs every time when trying to run testBrokerFailure in the
>> > > > ProducerFailureHangingTest suite.
>> > > >
>> > > > It was working for a time, but I updated to trunk HEAD and it's no
>> > longer
>> > > > working.
>> > > > I'm running on OSX with JDK 1.6.0_65.
>> > > > I tried increasing the HeapSize for the test target, but hit the
>> same
>> > > > issue.
>> > > > Running against 3f1a9c4cee778d089d3ec3167555c2b89cdc48bb
>> > > >
>> > > > Would appreciate any help.
>> > > > Regards,
>> > > > Dave
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > -- Guozhang
>> > >
>> >
>>
>>
>>
>> --
>> -- Guozhang
>>
>
>


-- 
-- Guozhang

Reply via email to