Unfortunately, the --tests syntax works for UnitTests but not IntegrationTests (which are run via the integrationTest task). For some reason it hangs. I'd really like our Gradle gurus to figure out a single, common syntax that works for running one test in any of our categories.
Anyone know why the following hangs? This reproduces for any IntegrationTest: <klund@pdx2-office-dhcp32>/Users/klund/dev/geode [589]$ ./gradlew geode-core:integrationTest --tests *LogMarkerJUnitTest :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-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 > Building 90% > :geode-core:integrationTest > 0 tests completed On Mon, Oct 3, 2016 at 10:23 AM, Kirk Lund <kl...@apache.org> wrote: > The --tests syntax works well for me. Thanks! > > > On Fri, Sep 30, 2016 at 4:18 PM, Jared Stewart <jstew...@pivotal.io> > wrote: > >> I don’t know why that happens, but I believe -Dtest.single has been >> deprecated in favor of --tests which lets you specify a test class pattern >> to match against. The following works for me: >> >> ./gradlew geode-core:test --tests *QueryDataFunctionApplyLimitClauseTest >> >> (Note that the * is necessary above to avoid having to fully qualify >> org.apache.geode.management.internal.beans.QueryDataFunction >> ApplyLimitClauseTest.) >> >> Best, >> Jared >> >> >> > On Sep 30, 2016, at 4:03 PM, Kirk Lund <kl...@apache.org> wrote: >> > >> > Does anyone know why "buildSrc:test" executes when I try to execute >> > "geode-core:test"? See my output below. Instead of executing >> > "geode-core:test", gradle executes "buildSrc:test" and fails with "Could >> > not find matching test for pattern" -- I think there's something broken >> in >> > our gradle files. >> > >> > Thanks, >> > Kirk >> > >> > <klund@pdx2-office-dhcp32>/Users/klund/dev/geode [530]$ find . -name >> > QueryDataFunctionApplyLimitClauseTest.java >> > ./geode-core/src/test/java/org/apache/geode/management/inter >> nal/beans/QueryDataFunctionApplyLimitClauseTest.java >> > >> > <klund@pdx2-office-dhcp32>/Users/klund/dev/geode [531]$ ./gradlew >> > geode-core:test -Dtest.single=QueryDataFunctionApplyLimitClauseTest >> > :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 FAILED >> > >> > FAILURE: Build failed with an exception. >> > >> > * What went wrong: >> > Execution failed for task ':test'. >> >> Could not find matching test for pattern: >> > QueryDataFunctionApplyLimitClauseTest >> > >> > * 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: 0.62 secs >> > <klund@pdx2-office-dhcp32>/Users/klund/dev/geode [532]$ >> >> >
