edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dale LaBossiere <dml.apa...@gmail.com>
Subject Re: tests showing UP-TO-DATE even after ./gradlew cleanTest
Date Thu, 16 Mar 2017 19:03:36 GMT
I think cleanTest is fine.  I ran it and then reran tests & reports and everything ran
and had “current” times.

I hadn’t looked closely at: what you had below…

cleanTest doesn’t clean artifacts from non-test tasks, e.g., :connectors:wsclient:classes,
so those tasks, that test depends on, will be reported as UP-TO-DATE

There are a couple of components, e.g., :connectors:serial, that lack any tests so there’s
nothing to rebuild/rerun for them following cleanTest - they’re reported UP-TO-DATE

> On Mar 16, 2017, at 1:54 PM, Katherine Marsden <kmarsden@apache.org> wrote:
> I ran ./gradlew cleanTest to clean up the tests but on rerun am seeing a lot of UP-TO-DATE
tests, e.g.
> connectors:serial:testClasses UP-TO-DATE
> :connectors:serial:test UP-TO-DATE
> :connectors:serial:testSummaryFinalizer
> :connectors:wsclient:compileJava UP-TO-DATE
> :connectors:wsclient:processResources UP-TO-DATE
> :connectors:wsclient:classes UP-TO-DATE
> :connectors:wsclient:jar UP-TO-DATE

View raw message