You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by Katherine Marsden <km...@apache.org> on 2017/03/16 17:54:50 UTC

tests showing UP-TO-DATE even after ./gradlew cleanTest

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

So, I am not really sure if I have actually run all the tests.
Below are the summary lines.  Does this output look like anything is 
missing?  How long should I expect the full run to take?

I assume the skipped ones are expected and require setup that I haven't 
done.

Best

Kathey


:analytics:math3 1.713sec SUCCESS (4 tests, 0 failures, 0 skipped)
:analytics:sensors 7.979sec SUCCESS (35 tests, 0 failures, 0 skipped)
:api:execution 0.859sec SUCCESS (2 tests, 0 failures, 0 skipped)
:api:function 0.884sec SUCCESS (8 tests, 0 failures, 0 skipped)
:api:oplet 0.860sec SUCCESS (3 tests, 0 failures, 0 skipped)
:api:topology 1.016sec SUCCESS (3 tests, 0 failures, 0 skipped)
:api:window 48.522sec SUCCESS (12 tests, 0 failures, 0 skipped)
:apps:iot 1.741sec SUCCESS (1 tests, 0 failures, 0 skipped)
:apps:runtime 6.200sec SUCCESS (1 tests, 0 failures, 0 skipped)
:connectors:command 31.771sec SUCCESS (12 tests, 0 failures, 0 skipped)
:connectors:csv 1.010sec SUCCESS (2 tests, 0 failures, 0 skipped)
:connectors:file 156.603sec SUCCESS (56 tests, 0 failures, 2 skipped)
:connectors:http 7.125sec SUCCESS (20 tests, 0 failures, 0 skipped)
:connectors:iot 0.904sec SUCCESS (1 tests, 0 failures, 0 skipped)
:connectors:jdbc 1.061sec SUCCESS (18 tests, 0 failures, 18 skipped)
:connectors:kafka 0.989sec SUCCESS (1 tests, 0 failures, 1 skipped)
:connectors:mqtt 89.730sec SUCCESS (24 tests, 0 failures, 0 skipped)
:connectors:pubsub 4.267sec SUCCESS (8 tests, 0 failures, 0 skipped)
:connectors:wsclient-javax.websocket 131.406sec SUCCESS (54 tests, 0 
failures, 0 skipped)
:console:server 2.169sec SUCCESS (8 tests, 0 failures, 0 skipped)
:providers:development 47.022sec SUCCESS (69 tests, 0 failures, 0 skipped)
:providers:direct 62.360sec SUCCESS (101 tests, 0 failures, 0 skipped)
:runtime:etiao 1.223sec SUCCESS (7 tests, 0 failures, 0 skipped)
:runtime:jmxcontrol 1.080sec SUCCESS (4 tests, 0 failures, 0 skipped)
:runtime:jobregistry 1.126sec SUCCESS (5 tests, 0 failures, 0 skipped)
:runtime:jsoncontrol 1.147sec SUCCESS (6 tests, 0 failures, 0 skipped)
:spi:topology 1.034sec SUCCESS (1 tests, 0 failures, 0 skipped)
:test:fvtiot 13.638sec SUCCESS (7 tests, 0 failures, 0 skipped)
:utils:metrics 0.903sec SUCCESS (6 tests, 0 failures, 0 skipped)


BUILD SUCCESSFUL
Total time: 10 mins 28.354 secs

Re: tests showing UP-TO-DATE even after ./gradlew cleanTest

Posted by Dale LaBossiere <dm...@gmail.com>.
Not that I know of.

— Dale

> On Mar 16, 2017, at 2:57 PM, Katherine Marsden <km...@apache.org> wrote:
> 
> One more question.  Is there a way I can point the tests to the convenience binary distribution?

Re: tests showing UP-TO-DATE even after ./gradlew cleanTest

Posted by Katherine Marsden <km...@apache.org>.
On 3/16/17 11:33 AM, Dale LaBossiere wrote:
> FWIW, a full run just took 12min for me.  479 tests run w/100% success, 21 skipped
>
> ./gradlew cleanAll
> ./gradlew test reports
>
> the report is in build/distributions/reports/tests/index.html
>
> Haven\u2019t yet played with cleanTest.
>

I get the same results 479 run, 21 skipped 100% success, so I will call 
that success. I do still see quite a few UP-TO-DATE's in the test run 
output, even after running cleanAll, but will assume I ran them at some 
point even if they didn't clean up totally.

One more question.  Is there a way I can point the tests to the 
convenience binary distribution?

Best

Kathey

Re: tests showing UP-TO-DATE even after ./gradlew cleanTest

Posted by Dale LaBossiere <dm...@gmail.com>.
FWIW, a full run just took 12min for me.  479 tests run w/100% success, 21 skipped

./gradlew cleanAll
./gradlew test reports

the report is in build/distributions/reports/tests/index.html

Haven’t yet played with cleanTest.

> On Mar 16, 2017, at 2:08 PM, Dale LaBossiere <dm...@gmail.com> wrote:
> 
> The only ones skipped should be jdbc, kafka, and non-open-mqtt connector tests.
> On OSX one of the FileSteams tests is also skipped.
> 
> If you run ./gradlew reports after/with test you can open your browser on the report file and get an easier to view report for all results.  
> 
> The results will aggregate the test runs in the sense that one test run that fails for whatever reason creates some results, then if you rerun test it will skip those successful completed ones and try to run those that didn’t complete successfully.  A report run will collect the latest state of test runs.
> 
> I think a full run takes >10min on my machine these days.
> 
> I’ll take a look at / try cleanTest, etc.
> 
> — Dale
> 
> 
>> On Mar 16, 2017, at 1:54 PM, Katherine Marsden <km...@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
>> 
>> So, I am not really sure if I have actually run all the tests.
>> Below are the summary lines.  Does this output look like anything is missing?  How long should I expect the full run to take?
>> 
>> I assume the skipped ones are expected and require setup that I haven't done.
>> 
>> Best
>> 
>> Kathey
>> 
>> 
>> :analytics:math3 1.713sec SUCCESS (4 tests, 0 failures, 0 skipped)
>> :analytics:sensors 7.979sec SUCCESS (35 tests, 0 failures, 0 skipped)
>> :api:execution 0.859sec SUCCESS (2 tests, 0 failures, 0 skipped)
>> :api:function 0.884sec SUCCESS (8 tests, 0 failures, 0 skipped)
>> :api:oplet 0.860sec SUCCESS (3 tests, 0 failures, 0 skipped)
>> :api:topology 1.016sec SUCCESS (3 tests, 0 failures, 0 skipped)
>> :api:window 48.522sec SUCCESS (12 tests, 0 failures, 0 skipped)
>> :apps:iot 1.741sec SUCCESS (1 tests, 0 failures, 0 skipped)
>> :apps:runtime 6.200sec SUCCESS (1 tests, 0 failures, 0 skipped)
>> :connectors:command 31.771sec SUCCESS (12 tests, 0 failures, 0 skipped)
>> :connectors:csv 1.010sec SUCCESS (2 tests, 0 failures, 0 skipped)
>> :connectors:file 156.603sec SUCCESS (56 tests, 0 failures, 2 skipped)
>> :connectors:http 7.125sec SUCCESS (20 tests, 0 failures, 0 skipped)
>> :connectors:iot 0.904sec SUCCESS (1 tests, 0 failures, 0 skipped)
>> :connectors:jdbc 1.061sec SUCCESS (18 tests, 0 failures, 18 skipped)
>> :connectors:kafka 0.989sec SUCCESS (1 tests, 0 failures, 1 skipped)
>> :connectors:mqtt 89.730sec SUCCESS (24 tests, 0 failures, 0 skipped)
>> :connectors:pubsub 4.267sec SUCCESS (8 tests, 0 failures, 0 skipped)
>> :connectors:wsclient-javax.websocket 131.406sec SUCCESS (54 tests, 0 failures, 0 skipped)
>> :console:server 2.169sec SUCCESS (8 tests, 0 failures, 0 skipped)
>> :providers:development 47.022sec SUCCESS (69 tests, 0 failures, 0 skipped)
>> :providers:direct 62.360sec SUCCESS (101 tests, 0 failures, 0 skipped)
>> :runtime:etiao 1.223sec SUCCESS (7 tests, 0 failures, 0 skipped)
>> :runtime:jmxcontrol 1.080sec SUCCESS (4 tests, 0 failures, 0 skipped)
>> :runtime:jobregistry 1.126sec SUCCESS (5 tests, 0 failures, 0 skipped)
>> :runtime:jsoncontrol 1.147sec SUCCESS (6 tests, 0 failures, 0 skipped)
>> :spi:topology 1.034sec SUCCESS (1 tests, 0 failures, 0 skipped)
>> :test:fvtiot 13.638sec SUCCESS (7 tests, 0 failures, 0 skipped)
>> :utils:metrics 0.903sec SUCCESS (6 tests, 0 failures, 0 skipped)
>> 
>> 
>> BUILD SUCCESSFUL
>> Total time: 10 mins 28.354 secs
>> 
>> 
>

Re: tests showing UP-TO-DATE even after ./gradlew cleanTest

Posted by Dale LaBossiere <dm...@gmail.com>.
The only ones skipped should be jdbc, kafka, and non-open-mqtt connector tests.
On OSX one of the FileSteams tests is also skipped.

If you run ./gradlew reports after/with test you can open your browser on the report file and get an easier to view report for all results.  

The results will aggregate the test runs in the sense that one test run that fails for whatever reason creates some results, then if you rerun test it will skip those successful completed ones and try to run those that didn’t complete successfully.  A report run will collect the latest state of test runs.

I think a full run takes >10min on my machine these days.

I’ll take a look at / try cleanTest, etc.

— Dale


> On Mar 16, 2017, at 1:54 PM, Katherine Marsden <km...@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
> 
> So, I am not really sure if I have actually run all the tests.
> Below are the summary lines.  Does this output look like anything is missing?  How long should I expect the full run to take?
> 
> I assume the skipped ones are expected and require setup that I haven't done.
> 
> Best
> 
> Kathey
> 
> 
> :analytics:math3 1.713sec SUCCESS (4 tests, 0 failures, 0 skipped)
> :analytics:sensors 7.979sec SUCCESS (35 tests, 0 failures, 0 skipped)
> :api:execution 0.859sec SUCCESS (2 tests, 0 failures, 0 skipped)
> :api:function 0.884sec SUCCESS (8 tests, 0 failures, 0 skipped)
> :api:oplet 0.860sec SUCCESS (3 tests, 0 failures, 0 skipped)
> :api:topology 1.016sec SUCCESS (3 tests, 0 failures, 0 skipped)
> :api:window 48.522sec SUCCESS (12 tests, 0 failures, 0 skipped)
> :apps:iot 1.741sec SUCCESS (1 tests, 0 failures, 0 skipped)
> :apps:runtime 6.200sec SUCCESS (1 tests, 0 failures, 0 skipped)
> :connectors:command 31.771sec SUCCESS (12 tests, 0 failures, 0 skipped)
> :connectors:csv 1.010sec SUCCESS (2 tests, 0 failures, 0 skipped)
> :connectors:file 156.603sec SUCCESS (56 tests, 0 failures, 2 skipped)
> :connectors:http 7.125sec SUCCESS (20 tests, 0 failures, 0 skipped)
> :connectors:iot 0.904sec SUCCESS (1 tests, 0 failures, 0 skipped)
> :connectors:jdbc 1.061sec SUCCESS (18 tests, 0 failures, 18 skipped)
> :connectors:kafka 0.989sec SUCCESS (1 tests, 0 failures, 1 skipped)
> :connectors:mqtt 89.730sec SUCCESS (24 tests, 0 failures, 0 skipped)
> :connectors:pubsub 4.267sec SUCCESS (8 tests, 0 failures, 0 skipped)
> :connectors:wsclient-javax.websocket 131.406sec SUCCESS (54 tests, 0 failures, 0 skipped)
> :console:server 2.169sec SUCCESS (8 tests, 0 failures, 0 skipped)
> :providers:development 47.022sec SUCCESS (69 tests, 0 failures, 0 skipped)
> :providers:direct 62.360sec SUCCESS (101 tests, 0 failures, 0 skipped)
> :runtime:etiao 1.223sec SUCCESS (7 tests, 0 failures, 0 skipped)
> :runtime:jmxcontrol 1.080sec SUCCESS (4 tests, 0 failures, 0 skipped)
> :runtime:jobregistry 1.126sec SUCCESS (5 tests, 0 failures, 0 skipped)
> :runtime:jsoncontrol 1.147sec SUCCESS (6 tests, 0 failures, 0 skipped)
> :spi:topology 1.034sec SUCCESS (1 tests, 0 failures, 0 skipped)
> :test:fvtiot 13.638sec SUCCESS (7 tests, 0 failures, 0 skipped)
> :utils:metrics 0.903sec SUCCESS (6 tests, 0 failures, 0 skipped)
> 
> 
> BUILD SUCCESSFUL
> Total time: 10 mins 28.354 secs
> 
>

Re: tests showing UP-TO-DATE even after ./gradlew cleanTest

Posted by Dale LaBossiere <dm...@gmail.com>.
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 <km...@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
> 
>