---
> ---
> Found suspect string in log4j at line 546
>
> -Original Message-
> From: Dan Smith [mailto:dsm...@pivotal.io]
> Sent: Tuesday, July 25, 2017 9:59 PM
> To: dev@geode.apache.org
> Subject: Re: Need to know complete execution time for geode-core Junit
ine 546
>
> -----Original Message-
> From: Dan Smith [mailto:dsm...@pivotal.io]
> Sent: Tuesday, July 25, 2017 9:59 PM
> To: dev@geode.apache.org
> Subject: Re: Need to know complete execution time for geode-core Junit
> tests
>
> What target are you running? It's
// this works properly.
I have i5 , 8GB laptop RAM.
Thanks,
Dinesh Akhand
-Original Message-
From: Dinesh Akhand
Sent: Monday, August 7, 2017 12:24 PM
To: dev@geode.apache.org
Subject: RE: Need to know complete execution time for geode-core Junit tests
Hi Team,
When we are running test
Akhand
---
Found suspect string in log4j at line 546
-Original Message-
From: Dan Smith [mailto:dsm...@pivotal.io]
Sent: Tuesday, July 25, 2017 9:59 PM
To: dev@geode.apache.org
Subject: Re: Need to know complete execution time for geode-core Junit tests
What target are you running? It's a bit confusing because there are
actually 3 different sets of tests. These times a really rough because I
don't have a good run in front of me, but this should give you an idea.
"True" unit tests, runs in 1-2 minutes like Jens Said:
./gradlew geode-core:test
Sin
You might want to get a few thread dumps to see if there is a hung test. Also,
make sure you have sufficient RAM.
Anthony
> On Jul 25, 2017, at 1:13 AM, Dinesh Akhand wrote:
>
> Hi Team,
>
> I trigger the geode-core Junit tests . it keeping running from last 3 hour.
> Can you please let me k
Hi Dinesh,
When I run '*./gradlew clean geode-core:test*', it takes about 1:30m on an
iMac.
How are you invoking the build? You can see the progress by tailing the
file: geode-core/build/test/test-progress.test.
--Jens
On Tue, Jul 25, 2017 at 1:13 AM, Dinesh Akhand wrote:
> Hi Team,
>
> I tr
