Hey, I was reviewing the 0.12.1 SBT upgrade patch and ran into a test
failing that was not there last I looked at the branch was 01/08 before
heading on vacation and not related to the patch I was reviewing (having
pulled a new clone to confirm things).

maybe something in KAFKA-648 changes cause this? I started looking at the
commits don't see anything glaring maybe some new timing issue? I tried on
two separate machines

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/

 

Joe,

Please can you enable DEBUG logging for the test, that will get you the
details of the failure. You will need to modify the log4j.properties file
in core/src/test/resources

Thanks,
Neha
On Sat, Jan 19, 2013 at 8:25 PM, Joe Stein <[EMAIL PROTECTED]> wrote:

> Hey, I was reviewing the 0.12.1 SBT upgrade patch and ran into a test
> failing that was not there last I looked at the branch was 01/08 before
> heading on vacation and not related to the patch I was reviewing (having
> pulled a new clone to confirm things).
>
> maybe something in KAFKA-648 changes cause this? I started looking at the
> commits don't see anything glaring maybe some new timing issue? I tried on
> two separate machines
>
> /*
> Joe Stein
> http://www.linkedin.com/in/charmalloc
> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> */
>

 

found the culprit looks like https://issues.apache.org/jira/browse/KAFKA-709

the fix I think is best to just update the AsyncProducerTest case for if
someone changes the new default value to something like 0 so it goes to
offer instead of put

adding the line props.put("queue.enqueue.timeout.ms", "0")

I will update the JIRA ticket and update the test so it passes
On Sun, Jan 20, 2013 at 1:30 PM, Neha Narkhede <[EMAIL PROTECTED]>wrote:

> Joe,
>
> Please can you enable DEBUG logging for the test, that will get you the
> details of the failure. You will need to modify the log4j.properties file
> in core/src/test/resources
>
> Thanks,
> Neha
>
>
> On Sat, Jan 19, 2013 at 8:25 PM, Joe Stein <[EMAIL PROTECTED]> wrote:
>
> > Hey, I was reviewing the 0.12.1 SBT upgrade patch and ran into a test
> > failing that was not there last I looked at the branch was 01/08 before
> > heading on vacation and not related to the patch I was reviewing (having
> > pulled a new clone to confirm things).
> >
> > maybe something in KAFKA-648 changes cause this? I started looking at the
> > commits don't see anything glaring maybe some new timing issue? I tried
> on
> > two separate machines
> >
> > /*
> > Joe Stein
> > http://www.linkedin.com/in/charmalloc
> > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> > */
> >
>

--

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/