Re: trunk unit test failure

The fix is committed on 0.8.1 branch and trunk now. /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop *

Re: trunk unit test failure

Ok, I can't upload a patch to JIRA because it keeps re-indexing itself ... =8^/ what I have found out and confirmed in testing is that ~/.gradle/gradle.properties overrides the local gradle.properties so we can keep (and have to it seems) the mavenXXX fields in there ... I was about to build the f

Re: trunk unit test failure

Taking a look now /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop / On Tue, Feb 18, 201

Re: trunk unit test failure

I tested this out. It seems that after the patch in https://issues.apache.org/jira/browse/KAFKA-1245, we need to update the gradle property file. Following up on that jira. Thanks, Jun On Tue, Feb 18, 2014 at 3:23 PM, Jun Rao wrote: > Actually, most people don't need to create the gradle.prop

Re: trunk unit test failure

Actually, most people don't need to create the gradle.properties file. You only need to do that if you plan to push artifacts to maven. Thanks, Jun On Mon, Feb 17, 2014 at 7:41 PM, Guozhang Wang wrote: > testSendToPartition is suppose to fail now since it detects some bugs in > the new produc

Re: trunk unit test failure

Jay. I think the plan is to ship a default in the final release, details in the RB: https://reviews.apache.org/r/17879/ For now just commenting out the @Test tag does not help since the junit test will still search for any functions with prefix test... So we need to change the function name as w

Re: trunk unit test failure

OK, it looks like JDK 7 problem. In my linux machine with JDK 6, unit tests were fine except new Producer one. Thank you On Tue, Feb 18, 2014 at 8:44 AM, Jay Kreps wrote: > Why do we need to create that gradle file? Can't we ship a default for > that? > > Also we should really comment out the

Re: trunk unit test failure

Why do we need to create that gradle file? Can't we ship a default for that? Also we should really comment out the @Test annotation on the failing test. I think we checked that in so I had a case to fix against but I think it is a bit disruptive. -Jay On Mon, Feb 17, 2014 at 7:41 PM, Guozhang W

Re: trunk unit test failure

testSendToPartition is suppose to fail now since it detects some bugs in the new producer code. We are working on it. For other test failures, I just redid the unit tests from trunk but does not see the failures. My test process: 1. Check out a new repository of trunk. 2. Create ~/.gradle/gradle.

Re: trunk unit test failure

Test failures are stable with the latest trunk, I am building Mac OSX with Java version "1.7.0_45" Java(TM) SE Runtime Environment (build 1.7.0_45-b18) Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode) The followings are log snippet from gradle build: kafka.server.LogOffsetTest > t

Re: trunk unit test failure

Is this error stable? could you check out a clean trunk and retry unit tests? Guozhang 2014-02-14 22:56 GMT-08:00 Bae, Jae Hyeon : >- LogOffsetTest . > > > testEmptyLogsGetOffsets >- LogOffsetTest . > > > testGetOffsetsBeforeEarliestTime >- LogOffsetTest . > > > testGetOffsets

trunk unit test failure

- LogOffsetTest . testEmptyLogsGetOffsets - LogOffsetTest . testGetOffsetsBeforeEarliestTime - LogOffsetTest . testGetOffsetsBeforeLatestTime - LogOffsetTest . testGetOffsetsBeforeNow - ProducerSendTest . testSendToPartition failed. Can I trust trunk? :)