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...@apache.org> on 2019/08/07 17:08:44 UTC
./gradlew test no longer runs/reruns tests?
I used to use "./gradlew test" to run or rerun unit tests but it no longer
works. It seems to just early out... maybe gradle thinks that the unit
tests were already run so it doesn't need to rerun them.
Is this intentional? I assume some gradle changes were made that changed
this behavior.
Re: ./gradlew test no longer runs/reruns tests?
Posted by Murtuza Boxwala <mb...@pivotal.io>.
To re-run tests it looks like the property is “forceTest”, so ./gradlew test -PforceTest should do the trick.
For diagnosing the javadocs, this might come in handy:
A neat gradle trick I like to use to see which dependent tasks will get run is the “-m” flag.
So something like "./gradlew -m build" will show all the tasks that will run without actually running them.
> On Aug 7, 2019, at 1:19 PM, Kirk Lund <kl...@apache.org> wrote:
>
> I have another question about an apparent change in "build". It looks like
> javadoc is no longer running if I do a "./gradlew build". Even "./gradlew
> clean build" doesn't generate all javadocs.
>
> *"./gradlew clean build" (or just "build") results in:*
>
> <kl...@Kirks-MacBook-Pro>/Users/klund/dev/gemfire/geode [640]$ find . -name
> "javadocs"
> ./geode-assembly/build/javadocs
> <kl...@Kirks-MacBook-Pro>/Users/klund/dev/gemfire/geode [641]$ find . -name
> "javadoc"
> ./geode-old-versions/1.9.0/build/apache-geode-1.9.0/javadoc
> ./geode-old-versions/1.3.0/build/apache-geode-1.3.0/javadoc
> ./geode-old-versions/1.7.0/build/apache-geode-1.7.0/javadoc
> ./geode-old-versions/1.4.0/build/apache-geode-1.4.0/javadoc
> ./geode-old-versions/1.5.0/build/apache-geode-1.5.0/javadoc
> ./geode-old-versions/1.2.0/build/apache-geode-1.2.0/javadoc
> ./geode-old-versions/1.8.0/build/apache-geode-1.8.0/javadoc
> ./geode-old-versions/1.6.0/build/apache-geode-1.6.0/javadoc
> ./geode-assembly/build/install/apache-geode/javadoc
>
> *"./gradlew javadoc" results in:*
>
> <kl...@Kirks-MacBook-Pro>/Users/klund/dev/geode3 [576]$ find . -name
> "javadocs"
> ./geode-assembly/build/javadocs
> <kl...@Kirks-MacBook-Pro>/Users/klund/dev/geode3 [577]$ find . -name
> "javadoc"
> ./geode-pulse/geode-pulse-test/build/javadoc
> ./geode-pulse/geode-pulse-test/build/tmp/javadoc
> ./geode-junit/build/javadoc
> ./geode-junit/build/tmp/javadoc
> ./geode-concurrency-test/build/javadoc
> ./geode-concurrency-test/build/tmp/javadoc
> ./geode-lucene/geode-lucene-test/build/javadoc
> ./geode-lucene/geode-lucene-test/build/tmp/javadoc
> ./geode-lucene/build/javadoc
> ./geode-lucene/build/tmp/javadoc
> ./geode-redis/build/javadoc
> ./geode-redis/build/tmp/javadoc
> ./geode-json/build/javadoc
> ./geode-json/build/tmp/javadoc
> ./geode-old-versions/1.9.0/build/apache-geode-1.9.0/javadoc
> ./geode-old-versions/1.3.0/build/apache-geode-1.3.0/javadoc
> ./geode-old-versions/1.7.0/build/apache-geode-1.7.0/javadoc
> ./geode-old-versions/1.4.0/build/apache-geode-1.4.0/javadoc
> ./geode-old-versions/1.5.0/build/apache-geode-1.5.0/javadoc
> ./geode-old-versions/1.2.0/build/apache-geode-1.2.0/javadoc
> ./geode-old-versions/1.8.0/build/apache-geode-1.8.0/javadoc
> ./geode-old-versions/1.6.0/build/apache-geode-1.6.0/javadoc
> ./geode-memcached/build/javadoc
> ./geode-memcached/build/tmp/javadoc
> ./geode-assembly/build/install/apache-geode/javadoc
> ./geode-assembly/geode-assembly-test/build/javadoc
> ./geode-assembly/geode-assembly-test/build/tmp/javadoc
> ./extensions/geode-modules-session/build/javadoc
> ./extensions/geode-modules-session/build/tmp/javadoc
> ./extensions/session-testing-war/build/javadoc
> ./extensions/session-testing-war/build/tmp/javadoc
> ./extensions/geode-modules-test/build/javadoc
> ./extensions/geode-modules-test/build/tmp/javadoc
> ./extensions/geode-modules-tomcat8/build/javadoc
> ./extensions/geode-modules-tomcat8/build/tmp/javadoc
> ./extensions/geode-modules-tomcat7/build/javadoc
> ./extensions/geode-modules-tomcat7/build/tmp/javadoc
> ./extensions/geode-modules-tomcat9/build/javadoc
> ./extensions/geode-modules-tomcat9/build/tmp/javadoc
> ./extensions/geode-modules/build/javadoc
> ./extensions/geode-modules/build/tmp/javadoc
> ./geode-management/build/javadoc
> ./geode-management/build/tmp/javadoc
> ./geode-rebalancer/build/javadoc
> ./geode-rebalancer/build/tmp/javadoc
> ./geode-dunit/build/javadoc
> ./geode-dunit/build/tmp/javadoc
> ./geode-core/build/javadoc
> ./geode-core/build/tmp/javadoc
> ./static-analysis/pmd-rules/build/javadoc
> ./static-analysis/pmd-rules/build/tmp/javadoc
> ./geode-protobuf/build/javadoc
> ./geode-protobuf/build/tmp/javadoc
> ./geode-common/build/javadoc
> ./geode-common/build/tmp/javadoc
> ./geode-experimental-driver/build/javadoc
> ./geode-experimental-driver/build/tmp/javadoc
> ./geode-connectors/build/javadoc
> ./geode-connectors/build/tmp/javadoc
> ./geode-old-client-support/build/javadoc
> ./geode-old-client-support/build/tmp/javadoc
>
> On Wed, Aug 7, 2019 at 10:13 AM Robert Houghton <rh...@pivotal.io>
> wrote:
>
>> We added a property to force test reruns specifically, but I can't remember
>> it off hand. More generally, is a gradle option to rerun all tasks (but
>> this takes longer) '--rerun-tasks'.
>>
>> On Wed, Aug 7, 2019, 10:09 Kirk Lund <kl...@apache.org> wrote:
>>
>>> I used to use "./gradlew test" to run or rerun unit tests but it no
>> longer
>>> works. It seems to just early out... maybe gradle thinks that the unit
>>> tests were already run so it doesn't need to rerun them.
>>>
>>> Is this intentional? I assume some gradle changes were made that changed
>>> this behavior.
>>>
>>
Re: ./gradlew test no longer runs/reruns tests?
Posted by Kirk Lund <kl...@apache.org>.
I have another question about an apparent change in "build". It looks like
javadoc is no longer running if I do a "./gradlew build". Even "./gradlew
clean build" doesn't generate all javadocs.
*"./gradlew clean build" (or just "build") results in:*
<kl...@Kirks-MacBook-Pro>/Users/klund/dev/gemfire/geode [640]$ find . -name
"javadocs"
./geode-assembly/build/javadocs
<kl...@Kirks-MacBook-Pro>/Users/klund/dev/gemfire/geode [641]$ find . -name
"javadoc"
./geode-old-versions/1.9.0/build/apache-geode-1.9.0/javadoc
./geode-old-versions/1.3.0/build/apache-geode-1.3.0/javadoc
./geode-old-versions/1.7.0/build/apache-geode-1.7.0/javadoc
./geode-old-versions/1.4.0/build/apache-geode-1.4.0/javadoc
./geode-old-versions/1.5.0/build/apache-geode-1.5.0/javadoc
./geode-old-versions/1.2.0/build/apache-geode-1.2.0/javadoc
./geode-old-versions/1.8.0/build/apache-geode-1.8.0/javadoc
./geode-old-versions/1.6.0/build/apache-geode-1.6.0/javadoc
./geode-assembly/build/install/apache-geode/javadoc
*"./gradlew javadoc" results in:*
<kl...@Kirks-MacBook-Pro>/Users/klund/dev/geode3 [576]$ find . -name
"javadocs"
./geode-assembly/build/javadocs
<kl...@Kirks-MacBook-Pro>/Users/klund/dev/geode3 [577]$ find . -name
"javadoc"
./geode-pulse/geode-pulse-test/build/javadoc
./geode-pulse/geode-pulse-test/build/tmp/javadoc
./geode-junit/build/javadoc
./geode-junit/build/tmp/javadoc
./geode-concurrency-test/build/javadoc
./geode-concurrency-test/build/tmp/javadoc
./geode-lucene/geode-lucene-test/build/javadoc
./geode-lucene/geode-lucene-test/build/tmp/javadoc
./geode-lucene/build/javadoc
./geode-lucene/build/tmp/javadoc
./geode-redis/build/javadoc
./geode-redis/build/tmp/javadoc
./geode-json/build/javadoc
./geode-json/build/tmp/javadoc
./geode-old-versions/1.9.0/build/apache-geode-1.9.0/javadoc
./geode-old-versions/1.3.0/build/apache-geode-1.3.0/javadoc
./geode-old-versions/1.7.0/build/apache-geode-1.7.0/javadoc
./geode-old-versions/1.4.0/build/apache-geode-1.4.0/javadoc
./geode-old-versions/1.5.0/build/apache-geode-1.5.0/javadoc
./geode-old-versions/1.2.0/build/apache-geode-1.2.0/javadoc
./geode-old-versions/1.8.0/build/apache-geode-1.8.0/javadoc
./geode-old-versions/1.6.0/build/apache-geode-1.6.0/javadoc
./geode-memcached/build/javadoc
./geode-memcached/build/tmp/javadoc
./geode-assembly/build/install/apache-geode/javadoc
./geode-assembly/geode-assembly-test/build/javadoc
./geode-assembly/geode-assembly-test/build/tmp/javadoc
./extensions/geode-modules-session/build/javadoc
./extensions/geode-modules-session/build/tmp/javadoc
./extensions/session-testing-war/build/javadoc
./extensions/session-testing-war/build/tmp/javadoc
./extensions/geode-modules-test/build/javadoc
./extensions/geode-modules-test/build/tmp/javadoc
./extensions/geode-modules-tomcat8/build/javadoc
./extensions/geode-modules-tomcat8/build/tmp/javadoc
./extensions/geode-modules-tomcat7/build/javadoc
./extensions/geode-modules-tomcat7/build/tmp/javadoc
./extensions/geode-modules-tomcat9/build/javadoc
./extensions/geode-modules-tomcat9/build/tmp/javadoc
./extensions/geode-modules/build/javadoc
./extensions/geode-modules/build/tmp/javadoc
./geode-management/build/javadoc
./geode-management/build/tmp/javadoc
./geode-rebalancer/build/javadoc
./geode-rebalancer/build/tmp/javadoc
./geode-dunit/build/javadoc
./geode-dunit/build/tmp/javadoc
./geode-core/build/javadoc
./geode-core/build/tmp/javadoc
./static-analysis/pmd-rules/build/javadoc
./static-analysis/pmd-rules/build/tmp/javadoc
./geode-protobuf/build/javadoc
./geode-protobuf/build/tmp/javadoc
./geode-common/build/javadoc
./geode-common/build/tmp/javadoc
./geode-experimental-driver/build/javadoc
./geode-experimental-driver/build/tmp/javadoc
./geode-connectors/build/javadoc
./geode-connectors/build/tmp/javadoc
./geode-old-client-support/build/javadoc
./geode-old-client-support/build/tmp/javadoc
On Wed, Aug 7, 2019 at 10:13 AM Robert Houghton <rh...@pivotal.io>
wrote:
> We added a property to force test reruns specifically, but I can't remember
> it off hand. More generally, is a gradle option to rerun all tasks (but
> this takes longer) '--rerun-tasks'.
>
> On Wed, Aug 7, 2019, 10:09 Kirk Lund <kl...@apache.org> wrote:
>
> > I used to use "./gradlew test" to run or rerun unit tests but it no
> longer
> > works. It seems to just early out... maybe gradle thinks that the unit
> > tests were already run so it doesn't need to rerun them.
> >
> > Is this intentional? I assume some gradle changes were made that changed
> > this behavior.
> >
>
Re: ./gradlew test no longer runs/reruns tests?
Posted by Robert Houghton <rh...@pivotal.io>.
We added a property to force test reruns specifically, but I can't remember
it off hand. More generally, is a gradle option to rerun all tasks (but
this takes longer) '--rerun-tasks'.
On Wed, Aug 7, 2019, 10:09 Kirk Lund <kl...@apache.org> wrote:
> I used to use "./gradlew test" to run or rerun unit tests but it no longer
> works. It seems to just early out... maybe gradle thinks that the unit
> tests were already run so it doesn't need to rerun them.
>
> Is this intentional? I assume some gradle changes were made that changed
> this behavior.
>
Re: ./gradlew test no longer runs/reruns tests?
Posted by Michael Oleske <mo...@pivotal.io>.
For more information/background on gradle and running tests, I suggest
reading this blog post from the gradle team
https://blog.gradle.org/stop-rerunning-tests
-michael
On Wed, Aug 7, 2019 at 11:58 AM Jacob Barrett <jb...@pivotal.io> wrote:
> Gradle has, for as long as I can recall, always had this behavior for unit
> tests. The default in Gradle Test plugin is to not rerun tests unless the
> main sources have changed. For integration, distributed and acceptance
> tests we have changed that default to always run regardless of source
> changes.
>
> > On Aug 7, 2019, at 10:08 AM, Kirk Lund <kl...@apache.org> wrote:
> >
> > I used to use "./gradlew test" to run or rerun unit tests but it no
> longer
> > works. It seems to just early out... maybe gradle thinks that the unit
> > tests were already run so it doesn't need to rerun them.
> >
> > Is this intentional? I assume some gradle changes were made that changed
> > this behavior.
>
Re: ./gradlew test no longer runs/reruns tests?
Posted by Jacob Barrett <jb...@pivotal.io>.
Gradle has, for as long as I can recall, always had this behavior for unit tests. The default in Gradle Test plugin is to not rerun tests unless the main sources have changed. For integration, distributed and acceptance tests we have changed that default to always run regardless of source changes.
> On Aug 7, 2019, at 10:08 AM, Kirk Lund <kl...@apache.org> wrote:
>
> I used to use "./gradlew test" to run or rerun unit tests but it no longer
> works. It seems to just early out... maybe gradle thinks that the unit
> tests were already run so it doesn't need to rerun them.
>
> Is this intentional? I assume some gradle changes were made that changed
> this behavior.