You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Kirk Lund <kl...@pivotal.io> on 2016/05/04 21:38:56 UTC
Unable to run single dunit
This used to work quite well for me. Why am I not able to run a single
dunit on the command-line now? Is this caused by the gradle upgrade?
<kl...@pdx2-office-dhcp32>/Users/klund/dev/gemfire/open [520]$ find . -name
ListAndDescribeDiskStoreCommandsDUnitTest.java
./geode-core/src/test/java/com/gemstone/gemfire/management/internal/cli/commands/ListAndDescribeDiskStoreCommandsDUnitTest.java
<kl...@pdx2-office-dhcp32>/Users/klund/dev/gemfire/open [521]$ ./gradlew
-DdistributedTest.single=ListAndDescribeDiskStoreCommandsDUnitTest
geode-core:distributedTest
:buildSrc:compileJava UP-TO-DATE
:buildSrc:compileGroovy UP-TO-DATE
:buildSrc:processResources UP-TO-DATE
:buildSrc:classes UP-TO-DATE
:buildSrc:jar UP-TO-DATE
:buildSrc:assemble UP-TO-DATE
:buildSrc:compileTestJava UP-TO-DATE
:buildSrc:compileTestGroovy UP-TO-DATE
:buildSrc:processTestResources UP-TO-DATE
:buildSrc:testClasses UP-TO-DATE
:buildSrc:test UP-TO-DATE
:buildSrc:check UP-TO-DATE
:buildSrc:build UP-TO-DATE
:geode-common:compileJava UP-TO-DATE
:geode-common:processResources UP-TO-DATE
:geode-common:classes UP-TO-DATE
:geode-common:jar UP-TO-DATE
:geode-joptsimple:compileJava UP-TO-DATE
:geode-joptsimple:processResources UP-TO-DATE
:geode-joptsimple:classes UP-TO-DATE
:geode-joptsimple:jar UP-TO-DATE
:geode-json:compileJava UP-TO-DATE
:geode-json:processResources UP-TO-DATE
:geode-json:classes UP-TO-DATE
:geode-json:jar UP-TO-DATE
:geode-core:compileJava UP-TO-DATE
:geode-core:createVersionPropertiesFile UP-TO-DATE
:geode-core:processResources UP-TO-DATE
:geode-core:classes UP-TO-DATE
:geode-junit:compileJava UP-TO-DATE
:geode-junit:processResources UP-TO-DATE
:geode-junit:classes UP-TO-DATE
:geode-junit:jar UP-TO-DATE
:geode-core:compileTestJava UP-TO-DATE
:geode-core:processTestResources UP-TO-DATE
:geode-core:testClasses UP-TO-DATE
:geode-core:distributedTest FAILED
:combineReports UP-TO-DATE
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':geode-core:distributedTest'.
> Could not find matching test for pattern:
ListAndDescribeDiskStoreCommandsDUnitTest
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output.
BUILD FAILED
Total time: 3.364 secs
Re: Unable to run single dunit
Posted by Dan Smith <ds...@pivotal.io>.
It also looks like this means these tests are not running as part of
precheckin! At least, I don't see ListAndDescribeDiskStoreCommandsDUnitTest
listed here
https://builds.apache.org/job/Geode-nightly/458/testReport/com.gemstone.gemfire.management.internal.cli.commands/
Somehow it's both not picking up the category in the distributedTest task,
but also not flagging it as a missed test in checkMissedTests. That's not
good.
-Dan
On Wed, May 4, 2016 at 4:19 PM, Kirk Lund <kl...@pivotal.io> wrote:
> Apparently any dunit test that uses a custom runner fails to run. But dunit
> tests using regular runners still run fine:
>
> 1) single dunit test with no custom runner (note this is a dunit test that
> has been updated to JUnit 4)
>
> $ ./gradlew -DdistributedTest.single=DistributedMemberDUnitTest
> geode-core:distributedTest
> ...
> :geode-core:distributedTest
> :combineReports
> All test reports at
> /export/latvia1/users/klund/dev/gemfire/open/build/reports/combined
>
> BUILD SUCCESSFUL
>
> Total time: 1 mins 26.859 secs
>
> 2) single dunit test using the JUnit 4 Parameterized runner (this is also a
> dunit test that has been updated to JUnit 4)
>
>
> $ ./gradlew
> -DdistributedTest.single=ListAndDescribeDiskStoreCommandsDUnitTest
> geode-core:distributedTest
> ...
> :geode-core:distributedTest FAILED
> :combineReports
> All test reports at
> /export/latvia1/users/klund/dev/gemfire/open/build/reports/combined
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':geode-core:distributedTest'.
> > Could not find matching test for pattern:
> ListAndDescribeDiskStoreCommandsDUnitTest
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
>
> BUILD FAILED
>
> Total time: 5.918 secs
>
>
> So, I would expect any dunit test using a custom runner (PowerMock,
> Parameterized, JUnitParamsRunner) would all fail if run individually in
> this way.
>
> -Kirk
>
>
> On Wed, May 4, 2016 at 2:38 PM, Kirk Lund <kl...@pivotal.io> wrote:
>
> > This used to work quite well for me. Why am I not able to run a single
> > dunit on the command-line now? Is this caused by the gradle upgrade?
> >
> > <kl...@pdx2-office-dhcp32>/Users/klund/dev/gemfire/open [520]$ find .
> > -name ListAndDescribeDiskStoreCommandsDUnitTest.java
> >
> >
> >
> ./geode-core/src/test/java/com/gemstone/gemfire/management/internal/cli/commands/ListAndDescribeDiskStoreCommandsDUnitTest.java
> >
> > <kl...@pdx2-office-dhcp32>/Users/klund/dev/gemfire/open [521]$ ./gradlew
> > -DdistributedTest.single=ListAndDescribeDiskStoreCommandsDUnitTest
> > geode-core:distributedTest
> >
> > :buildSrc:compileJava UP-TO-DATE
> > :buildSrc:compileGroovy UP-TO-DATE
> > :buildSrc:processResources UP-TO-DATE
> > :buildSrc:classes UP-TO-DATE
> > :buildSrc:jar UP-TO-DATE
> > :buildSrc:assemble UP-TO-DATE
> > :buildSrc:compileTestJava UP-TO-DATE
> > :buildSrc:compileTestGroovy UP-TO-DATE
> > :buildSrc:processTestResources UP-TO-DATE
> > :buildSrc:testClasses UP-TO-DATE
> > :buildSrc:test UP-TO-DATE
> > :buildSrc:check UP-TO-DATE
> > :buildSrc:build UP-TO-DATE
> > :geode-common:compileJava UP-TO-DATE
> > :geode-common:processResources UP-TO-DATE
> > :geode-common:classes UP-TO-DATE
> > :geode-common:jar UP-TO-DATE
> > :geode-joptsimple:compileJava UP-TO-DATE
> > :geode-joptsimple:processResources UP-TO-DATE
> > :geode-joptsimple:classes UP-TO-DATE
> > :geode-joptsimple:jar UP-TO-DATE
> > :geode-json:compileJava UP-TO-DATE
> > :geode-json:processResources UP-TO-DATE
> > :geode-json:classes UP-TO-DATE
> > :geode-json:jar UP-TO-DATE
> > :geode-core:compileJava UP-TO-DATE
> > :geode-core:createVersionPropertiesFile UP-TO-DATE
> > :geode-core:processResources UP-TO-DATE
> > :geode-core:classes UP-TO-DATE
> > :geode-junit:compileJava UP-TO-DATE
> > :geode-junit:processResources UP-TO-DATE
> > :geode-junit:classes UP-TO-DATE
> > :geode-junit:jar UP-TO-DATE
> > :geode-core:compileTestJava UP-TO-DATE
> > :geode-core:processTestResources UP-TO-DATE
> > :geode-core:testClasses UP-TO-DATE
> > :geode-core:distributedTest FAILED
> > :combineReports UP-TO-DATE
> >
> > FAILURE: Build failed with an exception.
> >
> > * What went wrong:
> > Execution failed for task ':geode-core:distributedTest'.
> > > Could not find matching test for pattern:
> > ListAndDescribeDiskStoreCommandsDUnitTest
> >
> > * Try:
> > Run with --stacktrace option to get the stack trace. Run with --info or
> > --debug option to get more log output.
> >
> > BUILD FAILED
> >
> > Total time: 3.364 secs
> >
> >
>
Re: Unable to run single dunit
Posted by Kirk Lund <kl...@pivotal.io>.
I described this problem in Jira GEODE-1350: Unable to use distributedTest
task to run a single DUnit test with a custom runner
DUnit tests that are annotated with @RunWith fail to execute when using
-DdistributedTest.single
-Kirk
On Wed, May 4, 2016 at 4:19 PM, Kirk Lund <kl...@pivotal.io> wrote:
> Apparently any dunit test that uses a custom runner fails to run. But
> dunit tests using regular runners still run fine:
>
> 1) single dunit test with no custom runner (note this is a dunit test that
> has been updated to JUnit 4)
>
> $ ./gradlew -DdistributedTest.single=DistributedMemberDUnitTest
> geode-core:distributedTest
> ...
> :geode-core:distributedTest
> :combineReports
> All test reports at
> /export/latvia1/users/klund/dev/gemfire/open/build/reports/combined
>
> BUILD SUCCESSFUL
>
> Total time: 1 mins 26.859 secs
>
> 2) single dunit test using the JUnit 4 Parameterized runner (this is also
> a dunit test that has been updated to JUnit 4)
>
>
> $ ./gradlew
> -DdistributedTest.single=ListAndDescribeDiskStoreCommandsDUnitTest
> geode-core:distributedTest
> ...
> :geode-core:distributedTest FAILED
> :combineReports
> All test reports at
> /export/latvia1/users/klund/dev/gemfire/open/build/reports/combined
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':geode-core:distributedTest'.
> > Could not find matching test for pattern:
> ListAndDescribeDiskStoreCommandsDUnitTest
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
>
> BUILD FAILED
>
> Total time: 5.918 secs
>
>
> So, I would expect any dunit test using a custom runner (PowerMock,
> Parameterized, JUnitParamsRunner) would all fail if run individually in
> this way.
>
> -Kirk
>
>
> On Wed, May 4, 2016 at 2:38 PM, Kirk Lund <kl...@pivotal.io> wrote:
>
>> This used to work quite well for me. Why am I not able to run a single
>> dunit on the command-line now? Is this caused by the gradle upgrade?
>>
>> <kl...@pdx2-office-dhcp32>/Users/klund/dev/gemfire/open [520]$ find .
>> -name ListAndDescribeDiskStoreCommandsDUnitTest.java
>>
>>
>> ./geode-core/src/test/java/com/gemstone/gemfire/management/internal/cli/commands/ListAndDescribeDiskStoreCommandsDUnitTest.java
>>
>> <kl...@pdx2-office-dhcp32>/Users/klund/dev/gemfire/open [521]$ ./gradlew
>> -DdistributedTest.single=ListAndDescribeDiskStoreCommandsDUnitTest
>> geode-core:distributedTest
>>
>> :buildSrc:compileJava UP-TO-DATE
>> :buildSrc:compileGroovy UP-TO-DATE
>> :buildSrc:processResources UP-TO-DATE
>> :buildSrc:classes UP-TO-DATE
>> :buildSrc:jar UP-TO-DATE
>> :buildSrc:assemble UP-TO-DATE
>> :buildSrc:compileTestJava UP-TO-DATE
>> :buildSrc:compileTestGroovy UP-TO-DATE
>> :buildSrc:processTestResources UP-TO-DATE
>> :buildSrc:testClasses UP-TO-DATE
>> :buildSrc:test UP-TO-DATE
>> :buildSrc:check UP-TO-DATE
>> :buildSrc:build UP-TO-DATE
>> :geode-common:compileJava UP-TO-DATE
>> :geode-common:processResources UP-TO-DATE
>> :geode-common:classes UP-TO-DATE
>> :geode-common:jar UP-TO-DATE
>> :geode-joptsimple:compileJava UP-TO-DATE
>> :geode-joptsimple:processResources UP-TO-DATE
>> :geode-joptsimple:classes UP-TO-DATE
>> :geode-joptsimple:jar UP-TO-DATE
>> :geode-json:compileJava UP-TO-DATE
>> :geode-json:processResources UP-TO-DATE
>> :geode-json:classes UP-TO-DATE
>> :geode-json:jar UP-TO-DATE
>> :geode-core:compileJava UP-TO-DATE
>> :geode-core:createVersionPropertiesFile UP-TO-DATE
>> :geode-core:processResources UP-TO-DATE
>> :geode-core:classes UP-TO-DATE
>> :geode-junit:compileJava UP-TO-DATE
>> :geode-junit:processResources UP-TO-DATE
>> :geode-junit:classes UP-TO-DATE
>> :geode-junit:jar UP-TO-DATE
>> :geode-core:compileTestJava UP-TO-DATE
>> :geode-core:processTestResources UP-TO-DATE
>> :geode-core:testClasses UP-TO-DATE
>> :geode-core:distributedTest FAILED
>> :combineReports UP-TO-DATE
>>
>> FAILURE: Build failed with an exception.
>>
>> * What went wrong:
>> Execution failed for task ':geode-core:distributedTest'.
>> > Could not find matching test for pattern:
>> ListAndDescribeDiskStoreCommandsDUnitTest
>>
>> * Try:
>> Run with --stacktrace option to get the stack trace. Run with --info or
>> --debug option to get more log output.
>>
>> BUILD FAILED
>>
>> Total time: 3.364 secs
>>
>>
>
Re: Unable to run single dunit
Posted by Kirk Lund <kl...@pivotal.io>.
Apparently any dunit test that uses a custom runner fails to run. But dunit
tests using regular runners still run fine:
1) single dunit test with no custom runner (note this is a dunit test that
has been updated to JUnit 4)
$ ./gradlew -DdistributedTest.single=DistributedMemberDUnitTest
geode-core:distributedTest
...
:geode-core:distributedTest
:combineReports
All test reports at
/export/latvia1/users/klund/dev/gemfire/open/build/reports/combined
BUILD SUCCESSFUL
Total time: 1 mins 26.859 secs
2) single dunit test using the JUnit 4 Parameterized runner (this is also a
dunit test that has been updated to JUnit 4)
$ ./gradlew
-DdistributedTest.single=ListAndDescribeDiskStoreCommandsDUnitTest
geode-core:distributedTest
...
:geode-core:distributedTest FAILED
:combineReports
All test reports at
/export/latvia1/users/klund/dev/gemfire/open/build/reports/combined
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':geode-core:distributedTest'.
> Could not find matching test for pattern:
ListAndDescribeDiskStoreCommandsDUnitTest
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output.
BUILD FAILED
Total time: 5.918 secs
So, I would expect any dunit test using a custom runner (PowerMock,
Parameterized, JUnitParamsRunner) would all fail if run individually in
this way.
-Kirk
On Wed, May 4, 2016 at 2:38 PM, Kirk Lund <kl...@pivotal.io> wrote:
> This used to work quite well for me. Why am I not able to run a single
> dunit on the command-line now? Is this caused by the gradle upgrade?
>
> <kl...@pdx2-office-dhcp32>/Users/klund/dev/gemfire/open [520]$ find .
> -name ListAndDescribeDiskStoreCommandsDUnitTest.java
>
>
> ./geode-core/src/test/java/com/gemstone/gemfire/management/internal/cli/commands/ListAndDescribeDiskStoreCommandsDUnitTest.java
>
> <kl...@pdx2-office-dhcp32>/Users/klund/dev/gemfire/open [521]$ ./gradlew
> -DdistributedTest.single=ListAndDescribeDiskStoreCommandsDUnitTest
> geode-core:distributedTest
>
> :buildSrc:compileJava UP-TO-DATE
> :buildSrc:compileGroovy UP-TO-DATE
> :buildSrc:processResources UP-TO-DATE
> :buildSrc:classes UP-TO-DATE
> :buildSrc:jar UP-TO-DATE
> :buildSrc:assemble UP-TO-DATE
> :buildSrc:compileTestJava UP-TO-DATE
> :buildSrc:compileTestGroovy UP-TO-DATE
> :buildSrc:processTestResources UP-TO-DATE
> :buildSrc:testClasses UP-TO-DATE
> :buildSrc:test UP-TO-DATE
> :buildSrc:check UP-TO-DATE
> :buildSrc:build UP-TO-DATE
> :geode-common:compileJava UP-TO-DATE
> :geode-common:processResources UP-TO-DATE
> :geode-common:classes UP-TO-DATE
> :geode-common:jar UP-TO-DATE
> :geode-joptsimple:compileJava UP-TO-DATE
> :geode-joptsimple:processResources UP-TO-DATE
> :geode-joptsimple:classes UP-TO-DATE
> :geode-joptsimple:jar UP-TO-DATE
> :geode-json:compileJava UP-TO-DATE
> :geode-json:processResources UP-TO-DATE
> :geode-json:classes UP-TO-DATE
> :geode-json:jar UP-TO-DATE
> :geode-core:compileJava UP-TO-DATE
> :geode-core:createVersionPropertiesFile UP-TO-DATE
> :geode-core:processResources UP-TO-DATE
> :geode-core:classes UP-TO-DATE
> :geode-junit:compileJava UP-TO-DATE
> :geode-junit:processResources UP-TO-DATE
> :geode-junit:classes UP-TO-DATE
> :geode-junit:jar UP-TO-DATE
> :geode-core:compileTestJava UP-TO-DATE
> :geode-core:processTestResources UP-TO-DATE
> :geode-core:testClasses UP-TO-DATE
> :geode-core:distributedTest FAILED
> :combineReports UP-TO-DATE
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':geode-core:distributedTest'.
> > Could not find matching test for pattern:
> ListAndDescribeDiskStoreCommandsDUnitTest
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
>
> BUILD FAILED
>
> Total time: 3.364 secs
>
>
Re: Unable to run single dunit
Posted by Kirk Lund <kl...@pivotal.io>.
This used to work. I've never tried with parentheses before but I just
confirmed that it does not work either...
./gradlew
-DdistributedTest.single="ListAndDescribeDiskStoreCommandsDUnitTest"
geode-core:distributedTest
:geode-core:distributedTest FAILED
:combineReports
All test reports at
/export/latvia1/users/klund/dev/gemfire/open/build/reports/combined
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':geode-core:distributedTest'.
> Could not find matching test for pattern:
ListAndDescribeDiskStoreCommandsDUnitTest
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output.
BUILD FAILED
Total time: 56.68 secs
On Wed, May 4, 2016 at 2:42 PM, Udo Kohlmeyer <uk...@pivotal.io> wrote:
> When I did this, I had to "wrap" the class with '*'
>
> The command is then.
>
> ./gradlew
> -DdistributedTest.single=*ListAndDescribeDiskStoreCommandsDUnitTest*
>
>
> On 5/05/2016 7:38 am, Kirk Lund wrote:
>
>> This used to work quite well for me. Why am I not able to run a single
>> dunit on the command-line now? Is this caused by the gradle upgrade?
>>
>> <kl...@pdx2-office-dhcp32>/Users/klund/dev/gemfire/open [520]$ find .
>> -name
>> ListAndDescribeDiskStoreCommandsDUnitTest.java
>>
>>
>> ./geode-core/src/test/java/com/gemstone/gemfire/management/internal/cli/commands/ListAndDescribeDiskStoreCommandsDUnitTest.java
>>
>> <kl...@pdx2-office-dhcp32>/Users/klund/dev/gemfire/open [521]$ ./gradlew
>> -DdistributedTest.single=ListAndDescribeDiskStoreCommandsDUnitTest
>> geode-core:distributedTest
>>
>> :buildSrc:compileJava UP-TO-DATE
>> :buildSrc:compileGroovy UP-TO-DATE
>> :buildSrc:processResources UP-TO-DATE
>> :buildSrc:classes UP-TO-DATE
>> :buildSrc:jar UP-TO-DATE
>> :buildSrc:assemble UP-TO-DATE
>> :buildSrc:compileTestJava UP-TO-DATE
>> :buildSrc:compileTestGroovy UP-TO-DATE
>> :buildSrc:processTestResources UP-TO-DATE
>> :buildSrc:testClasses UP-TO-DATE
>> :buildSrc:test UP-TO-DATE
>> :buildSrc:check UP-TO-DATE
>> :buildSrc:build UP-TO-DATE
>> :geode-common:compileJava UP-TO-DATE
>> :geode-common:processResources UP-TO-DATE
>> :geode-common:classes UP-TO-DATE
>> :geode-common:jar UP-TO-DATE
>> :geode-joptsimple:compileJava UP-TO-DATE
>> :geode-joptsimple:processResources UP-TO-DATE
>> :geode-joptsimple:classes UP-TO-DATE
>> :geode-joptsimple:jar UP-TO-DATE
>> :geode-json:compileJava UP-TO-DATE
>> :geode-json:processResources UP-TO-DATE
>> :geode-json:classes UP-TO-DATE
>> :geode-json:jar UP-TO-DATE
>> :geode-core:compileJava UP-TO-DATE
>> :geode-core:createVersionPropertiesFile UP-TO-DATE
>> :geode-core:processResources UP-TO-DATE
>> :geode-core:classes UP-TO-DATE
>> :geode-junit:compileJava UP-TO-DATE
>> :geode-junit:processResources UP-TO-DATE
>> :geode-junit:classes UP-TO-DATE
>> :geode-junit:jar UP-TO-DATE
>> :geode-core:compileTestJava UP-TO-DATE
>> :geode-core:processTestResources UP-TO-DATE
>> :geode-core:testClasses UP-TO-DATE
>> :geode-core:distributedTest FAILED
>> :combineReports UP-TO-DATE
>>
>> FAILURE: Build failed with an exception.
>>
>> * What went wrong:
>> Execution failed for task ':geode-core:distributedTest'.
>>
>>> Could not find matching test for pattern:
>>>
>> ListAndDescribeDiskStoreCommandsDUnitTest
>>
>> * Try:
>> Run with --stacktrace option to get the stack trace. Run with --info or
>> --debug option to get more log output.
>>
>> BUILD FAILED
>>
>> Total time: 3.364 secs
>>
>>
>
Re: Unable to run single dunit
Posted by Udo Kohlmeyer <uk...@pivotal.io>.
When I did this, I had to "wrap" the class with '*'
The command is then.
./gradlew
-DdistributedTest.single=*ListAndDescribeDiskStoreCommandsDUnitTest*
On 5/05/2016 7:38 am, Kirk Lund wrote:
> This used to work quite well for me. Why am I not able to run a single
> dunit on the command-line now? Is this caused by the gradle upgrade?
>
> <kl...@pdx2-office-dhcp32>/Users/klund/dev/gemfire/open [520]$ find . -name
> ListAndDescribeDiskStoreCommandsDUnitTest.java
>
> ./geode-core/src/test/java/com/gemstone/gemfire/management/internal/cli/commands/ListAndDescribeDiskStoreCommandsDUnitTest.java
>
> <kl...@pdx2-office-dhcp32>/Users/klund/dev/gemfire/open [521]$ ./gradlew
> -DdistributedTest.single=ListAndDescribeDiskStoreCommandsDUnitTest
> geode-core:distributedTest
>
> :buildSrc:compileJava UP-TO-DATE
> :buildSrc:compileGroovy UP-TO-DATE
> :buildSrc:processResources UP-TO-DATE
> :buildSrc:classes UP-TO-DATE
> :buildSrc:jar UP-TO-DATE
> :buildSrc:assemble UP-TO-DATE
> :buildSrc:compileTestJava UP-TO-DATE
> :buildSrc:compileTestGroovy UP-TO-DATE
> :buildSrc:processTestResources UP-TO-DATE
> :buildSrc:testClasses UP-TO-DATE
> :buildSrc:test UP-TO-DATE
> :buildSrc:check UP-TO-DATE
> :buildSrc:build UP-TO-DATE
> :geode-common:compileJava UP-TO-DATE
> :geode-common:processResources UP-TO-DATE
> :geode-common:classes UP-TO-DATE
> :geode-common:jar UP-TO-DATE
> :geode-joptsimple:compileJava UP-TO-DATE
> :geode-joptsimple:processResources UP-TO-DATE
> :geode-joptsimple:classes UP-TO-DATE
> :geode-joptsimple:jar UP-TO-DATE
> :geode-json:compileJava UP-TO-DATE
> :geode-json:processResources UP-TO-DATE
> :geode-json:classes UP-TO-DATE
> :geode-json:jar UP-TO-DATE
> :geode-core:compileJava UP-TO-DATE
> :geode-core:createVersionPropertiesFile UP-TO-DATE
> :geode-core:processResources UP-TO-DATE
> :geode-core:classes UP-TO-DATE
> :geode-junit:compileJava UP-TO-DATE
> :geode-junit:processResources UP-TO-DATE
> :geode-junit:classes UP-TO-DATE
> :geode-junit:jar UP-TO-DATE
> :geode-core:compileTestJava UP-TO-DATE
> :geode-core:processTestResources UP-TO-DATE
> :geode-core:testClasses UP-TO-DATE
> :geode-core:distributedTest FAILED
> :combineReports UP-TO-DATE
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':geode-core:distributedTest'.
>> Could not find matching test for pattern:
> ListAndDescribeDiskStoreCommandsDUnitTest
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
>
> BUILD FAILED
>
> Total time: 3.364 secs
>