You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Dinesh Akhand <di...@amdocs.com> on 2017/07/25 08:13:58 UTC
Need to know complete execution time for geode-core Junit tests
Hi Team,
I trigger the geode-core Junit tests . it keeping running from last 3 hour.
Can you please let me know how much time it take completion of Junit test in Geode-core.
I am using geode 1.1.1
Thanks,
Dinesh Akhand
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
RE: Need to know complete execution time for geode-core Junit tests
Posted by Dinesh Akhand <di...@amdocs.com>.
Hi Team,
When we run :
./gradlew integrationTest
./gradlew distributedTest
Many test are getting failed with head allocation error or configuration error.
Can you please suggest , what extra configuration we need to do .
I am able to run Junit correctly.
unit tests - run with ./gradlew test // 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 on windows : we are getting below error We ran : gradlew precheckin
rg.apache.geode.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest > test003StartServerFailsFastOnMissingCacheXmlFile FAILED
java.lang.AssertionError:
Warning: The Geode cache XML file C:\path\to\missing\cache.xml could not be found.
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.apache.geode.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test003StartServerFailsFastOnMissingCacheXmlFile(LauncherLifecycleCommandsDUnitTest.java:502)
org.apache.geode.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest > test004StartServerFailsFastOnMissingGemFirePropertiesFile FAILED
java.lang.AssertionError:
Warning: The Geode properties file C:\path\to\missing\gemfire.properties could not be found.
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at
Is there any path we need to set in windows to make it run.
Thanks,
Dinesh Akhand
-----------------------------------------------------------------------
Found suspect string in log4j at line 546
-----Original Message-----
From: Dan Smith [mailto:dsmith@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
Single VM integration tests - runs in maybe 1.5 hours:
./gradlew geode-core:integrationTest
Multiple VM integration tests - runs in maybe 5 hours?
.gradlew geode-core:distributedTest
Run all of the tests
./gradlew geode-core:precheckin
-Dan
On Tue, Jul 25, 2017 at 8:34 AM, Anthony Baker <ab...@pivotal.io> wrote:
> 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 <di...@amdocs.com> wrote:
> >
> > Hi Team,
> >
> > I trigger the geode-core Junit tests . it keeping running from last
> > 3
> hour.
> > Can you please let me know how much time it take completion of Junit
> test in Geode-core.
> > I am using geode 1.1.1
> >
> >
> > Thanks,
> > Dinesh Akhand
> > This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>
>
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
RE: Need to know complete execution time for geode-core Junit tests
Posted by Dinesh Akhand <di...@amdocs.com>.
Thanks Darrel It works on Linux.
But there I see another failure:
:geode-core:distributedTest
org.apache.geode.internal.cache.FixedPRSinglehopDUnitTest > testMetadataInClientWithFixedPartitions FAILED
java.lang.AssertionError: bucket 3 was incorrect expected:<20189> but was:<29785>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.apache.geode.internal.cache.FixedPRSinglehopDUnitTest.testMetadataInClientWithFixedPartitions(FixedPRSinglehopDUnitTest.java:352)
Which all test are part of Geode CI . only Junit ? or Integration ? distributedTest?
Thanks,
Dinesh Akhand
-----Original Message-----
From: Darrel Schneider [mailto:dschneider@pivotal.io]
Sent: Monday, August 7, 2017 9:59 PM
To: dev@geode.apache.org
Subject: Re: Need to know complete execution time for geode-core Junit tests
For test004StartServerFailsFastOnMissingGemFirePropertiesFile I think this test just needs to be improved for Windows.
The test has an assertion that the failure message contains a certain string. On Windows the message contains "C:" and "\" which the test does not expect. Instead of the test treating "cacheXmlPathName" as a constant I think it should create an instance of File using cacheXmlPathName and then make sure the message contains the result of calling getAbsolutePath on that File.
On Sun, Aug 6, 2017 at 11:54 PM, Dinesh Akhand <di...@amdocs.com> wrote:
> Hi Team,
>
> When we are running test on windows : we are getting below error We
> ran : gradlew precheckin
>
>
> rg.apache.geode.management.internal.cli.commands.
> LauncherLifecycleCommandsDUnitTest >
> test003StartServerFailsFastOnMissingCacheXmlFile
> FAILED
> java.lang.AssertionError:
> Warning: The Geode cache XML file C:\path\to\missing\cache.xml
> could not be found.
>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.apache.geode.management.internal.cli.commands.
> LauncherLifecycleCommandsDUnitTest.test003StartServerFailsFastOnM
> issingCacheXmlFile(LauncherLifecycleCommandsDUnitTest.java:502)
>
> org.apache.geode.management.internal.cli.commands.
> LauncherLifecycleCommandsDUnitTest >
> test004StartServerFailsFastOnMissingGemFirePropertiesFile
> FAILED
> java.lang.AssertionError:
> Warning: The Geode properties file
> C:\path\to\missing\gemfire.properties
> could not be found.
>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at
>
> Is there any path we need to set in windows to make it run.
>
> Thanks,
> Dinesh Akhand
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------------------------------------
> -----------
> Found suspect string in log4j at line 546
>
> -----Original Message-----
> From: Dan Smith [mailto:dsmith@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
>
> Single VM integration tests - runs in maybe 1.5 hours:
> ./gradlew geode-core:integrationTest
>
> Multiple VM integration tests - runs in maybe 5 hours?
> .gradlew geode-core:distributedTest
>
> Run all of the tests
> ./gradlew geode-core:precheckin
>
> -Dan
>
> On Tue, Jul 25, 2017 at 8:34 AM, Anthony Baker <ab...@pivotal.io> wrote:
>
> > 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 <di...@amdocs.com>
> wrote:
> > >
> > > Hi Team,
> > >
> > > I trigger the geode-core Junit tests . it keeping running from
> > > last
> > > 3
> > hour.
> > > Can you please let me know how much time it take completion of
> > > Junit
> > test in Geode-core.
> > > I am using geode 1.1.1
> > >
> > >
> > > Thanks,
> > > Dinesh Akhand
> > > This message and the information contained herein is proprietary
> > > and
> > confidential and subject to the Amdocs policy statement,
> > >
> > > you may review at https://www.amdocs.com/about/email-disclaimer <
> > https://www.amdocs.com/about/email-disclaimer>
> >
> >
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
Re: Need to know complete execution time for geode-core Junit tests
Posted by Darrel Schneider <ds...@pivotal.io>.
For test004StartServerFailsFastOnMissingGemFirePropertiesFile I think this
test just needs to be improved for Windows.
The test has an assertion that the failure message contains a certain
string. On Windows the message contains "C:" and "\" which the test does
not expect. Instead of the test treating "cacheXmlPathName" as a constant I
think it should create an instance of File using cacheXmlPathName and then
make sure the message contains the result of calling getAbsolutePath on
that File.
On Sun, Aug 6, 2017 at 11:54 PM, Dinesh Akhand <di...@amdocs.com> wrote:
> Hi Team,
>
> When we are running test on windows : we are getting below error
> We ran : gradlew precheckin
>
>
> rg.apache.geode.management.internal.cli.commands.
> LauncherLifecycleCommandsDUnitTest > test003StartServerFailsFastOnMissingCacheXmlFile
> FAILED
> java.lang.AssertionError:
> Warning: The Geode cache XML file C:\path\to\missing\cache.xml could
> not be found.
>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.apache.geode.management.internal.cli.commands.
> LauncherLifecycleCommandsDUnitTest.test003StartServerFailsFastOnM
> issingCacheXmlFile(LauncherLifecycleCommandsDUnitTest.java:502)
>
> org.apache.geode.management.internal.cli.commands.
> LauncherLifecycleCommandsDUnitTest > test004StartServerFailsFastOnMissingGemFirePropertiesFile
> FAILED
> java.lang.AssertionError:
> Warning: The Geode properties file C:\path\to\missing\gemfire.properties
> could not be found.
>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at
>
> Is there any path we need to set in windows to make it run.
>
> Thanks,
> Dinesh Akhand
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------------------------------------
> -----------
> Found suspect string in log4j at line 546
>
> -----Original Message-----
> From: Dan Smith [mailto:dsmith@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
>
> Single VM integration tests - runs in maybe 1.5 hours:
> ./gradlew geode-core:integrationTest
>
> Multiple VM integration tests - runs in maybe 5 hours?
> .gradlew geode-core:distributedTest
>
> Run all of the tests
> ./gradlew geode-core:precheckin
>
> -Dan
>
> On Tue, Jul 25, 2017 at 8:34 AM, Anthony Baker <ab...@pivotal.io> wrote:
>
> > 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 <di...@amdocs.com>
> wrote:
> > >
> > > Hi Team,
> > >
> > > I trigger the geode-core Junit tests . it keeping running from last
> > > 3
> > hour.
> > > Can you please let me know how much time it take completion of Junit
> > test in Geode-core.
> > > I am using geode 1.1.1
> > >
> > >
> > > Thanks,
> > > Dinesh Akhand
> > > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> > >
> > > you may review at https://www.amdocs.com/about/email-disclaimer <
> > https://www.amdocs.com/about/email-disclaimer>
> >
> >
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>
RE: Need to know complete execution time for geode-core Junit tests
Posted by Dinesh Akhand <di...@amdocs.com>.
Hi Team,
When we are running test on windows : we are getting below error
We ran : gradlew precheckin
rg.apache.geode.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest > test003StartServerFailsFastOnMissingCacheXmlFile FAILED
java.lang.AssertionError:
Warning: The Geode cache XML file C:\path\to\missing\cache.xml could not be found.
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.apache.geode.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test003StartServerFailsFastOnMissingCacheXmlFile(LauncherLifecycleCommandsDUnitTest.java:502)
org.apache.geode.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest > test004StartServerFailsFastOnMissingGemFirePropertiesFile FAILED
java.lang.AssertionError:
Warning: The Geode properties file C:\path\to\missing\gemfire.properties could not be found.
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at
Is there any path we need to set in windows to make it run.
Thanks,
Dinesh Akhand
-----------------------------------------------------------------------
Found suspect string in log4j at line 546
-----Original Message-----
From: Dan Smith [mailto:dsmith@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
Single VM integration tests - runs in maybe 1.5 hours:
./gradlew geode-core:integrationTest
Multiple VM integration tests - runs in maybe 5 hours?
.gradlew geode-core:distributedTest
Run all of the tests
./gradlew geode-core:precheckin
-Dan
On Tue, Jul 25, 2017 at 8:34 AM, Anthony Baker <ab...@pivotal.io> wrote:
> 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 <di...@amdocs.com> wrote:
> >
> > Hi Team,
> >
> > I trigger the geode-core Junit tests . it keeping running from last
> > 3
> hour.
> > Can you please let me know how much time it take completion of Junit
> test in Geode-core.
> > I am using geode 1.1.1
> >
> >
> > Thanks,
> > Dinesh Akhand
> > This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>
>
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
Re: Need to know complete execution time for geode-core Junit tests
Posted by Dan Smith <ds...@pivotal.io>.
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
Single VM integration tests - runs in maybe 1.5 hours:
./gradlew geode-core:integrationTest
Multiple VM integration tests - runs in maybe 5 hours?
.gradlew geode-core:distributedTest
Run all of the tests
./gradlew geode-core:precheckin
-Dan
On Tue, Jul 25, 2017 at 8:34 AM, Anthony Baker <ab...@pivotal.io> wrote:
> 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 <di...@amdocs.com> wrote:
> >
> > Hi Team,
> >
> > I trigger the geode-core Junit tests . it keeping running from last 3
> hour.
> > Can you please let me know how much time it take completion of Junit
> test in Geode-core.
> > I am using geode 1.1.1
> >
> >
> > Thanks,
> > Dinesh Akhand
> > This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>
>
Re: Need to know complete execution time for geode-core Junit tests
Posted by Anthony Baker <ab...@pivotal.io>.
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 <di...@amdocs.com> wrote:
>
> Hi Team,
>
> I trigger the geode-core Junit tests . it keeping running from last 3 hour.
> Can you please let me know how much time it take completion of Junit test in Geode-core.
> I am using geode 1.1.1
>
>
> Thanks,
> Dinesh Akhand
> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
Re: Need to know complete execution time for geode-core Junit tests
Posted by Jens Deppe <jd...@pivotal.io>.
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 <di...@amdocs.com> wrote:
> Hi Team,
>
> I trigger the geode-core Junit tests . it keeping running from last 3 hour.
> Can you please let me know how much time it take completion of Junit test
> in Geode-core.
> I am using geode 1.1.1
>
>
> Thanks,
> Dinesh Akhand
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>