I guess its just my machine then. Thanks!
On Mon, Mar 2, 2015 at 2:47 PM, Guozhang Wang <[email protected]> wrote: > Here are some number I got (this is with KAFKA-1910 patch and ConsumerTest > modified a bit): > > ---- JDK 8 ---- > > Total time: 18 mins 3.649 secs > > real 18m4.091s > user 0m7.105s > sys 0m0.426s > > ---- JDK 7 ---- > > Total time: 18 mins 55.546 secs > > real 18m55.997s > user 0m4.157s > sys 0m0.341s > > -------------------- > > Guozhang > > > > On Wed, Feb 25, 2015 at 5:06 PM, Guozhang Wang <[email protected]> > wrote: > >> I am working on the test handing / NPE / failure issues of ConsumerTest >> only. >> >> I currently run Java 8 and the unit test takes about 10 minutes, I can do >> "time ./gradlew test" with both versions and see if there is a clear >> difference. >> >> Guozhang >> ________________________________ >> From: Jay Kreps [[email protected]] >> Sent: Wednesday, February 25, 2015 4:53 PM >> To: [email protected]; Guozhang Wang >> Subject: Re: Unit tests in java7 vs java8 >> >> Yeah, hey Guozhang, is that fix part of the larger consumer patch you just >> posted or is that a separate issue? >> >> -Jay >> >> On Wed, Feb 25, 2015 at 4:25 PM, Gwen Shapira <[email protected] >> <mailto:[email protected]>> wrote: >> The Consumer tests are currently hanging :( >> >> I think Guozhang is working on a solution. I'm commenting them out until >> the problem is resolved... >> >> >> >> On Wed, Feb 25, 2015 at 4:00 PM, Tong Li <[email protected]<mailto: >> [email protected]>> wrote: >> >> > Gwen, >> > I have not tried Java 8. Still on Java 7, but I always run into the >> > test hung problems (no errors on the screen and the system is completely >> > idle), it may be a different problem. I can recreate that problem every >> > time when I run "gradle --daemon testAll", I recall that couple of weeks >> > ago there was one patch saying fixed the problem, but I am still seeing >> the >> > problem with latest code. What I noticed is that seems tests always stop >> at >> > one of the ConsumerTest test cases. What puzzled me the most is that it >> was >> > not always a particular test case. Being very new in this community, I >> > think that error must be something related to my env. Here is my >> > environment: >> > >> > Oracle JDK 7, gradle 2.2.1, scala 2.10.4. Lot of open file handles and >> > big enough max lock memory, >> > >> > not complaining, just some observations in case you wonder what other >> > developers may face. >> > >> > Thanks. >> > >> > Tong Li >> > OpenStack & Kafka Community Development >> > Building 501/B205 >> > [email protected]<mailto:[email protected]> >> > >> > [image: Inactive hide details for Gwen Shapira ---02/25/2015 03:47:58 >> > PM---Hi, Anyone running tests on Java 8? I just noticed that they]Gwen >> > Shapira ---02/25/2015 03:47:58 PM---Hi, Anyone running tests on Java 8? I >> > just noticed that they take almost twice >> > >> > From: Gwen Shapira <[email protected]<mailto:[email protected]>> >> > To: "[email protected]<mailto:[email protected]>" < >> [email protected]<mailto:[email protected]>> >> > Date: 02/25/2015 03:47 PM >> > Subject: Unit tests in java7 vs java8 >> > ------------------------------ >> > >> > >> > >> > Hi, >> > >> > Anyone running tests on Java 8? I just noticed that they take almost >> twice >> > as long to run compared to Java 7 (at least on my box, and with Scala >> > 2.10.4). >> > >> > Anyone else noticed this? Maybe even did some digging on the causes? >> > >> > Gwen >> > >> > >> >> > > > -- > -- Guozhang
