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
On 3/16/17 9:34 AM, Katherine Marsden wrote:
* What went wrong:
Execution failed for task ':connectors:wsclient-javax.websocket:test'.
There were failing tests. See the results at:
/edgent/releasetesting1.1/edgent-1.1.0-src/connectors/wsclient-javax.websocket/build/test-results/test/
Note:
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
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
The web socket tests run against a public web socket server. It’s possible
that it was acting up briefly. I haven’t seen problems on my OSX Sierra fwiw.
> On Mar 16, 2017, at 1:01 PM, Katherine Marsden wrote:
>
> On 3/16/17 9:34 AM, Katherine Marsden wrote:
>
>>
>> *
Hello
I am testing the release candidate on MacOS Sierra 10.12.1 and get the
failure below
On a quick search of Jira, I didn't see it. I haven't looked at the
code yet but was wondering if anyone has seen this before.
Best
Kathey
* What went wrong:
Execution failed for task
Hey buddy, can you spare a VOTE? :-)
Just another ping. I appreciate that folks may have a lot of things on their
plate at this time.
Thanks in advance for your help in getting this release out the door.
— Dale
> On Mar 5, 2017, at 7:58 AM, Dale LaBossiere wrote:
>
>
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
+1
On Thu, Mar 16, 2017 at 5:11 AM, Dale LaBossiere wrote:
> Hey buddy, can you spare a VOTE? :-)
>
> Just another ping. I appreciate that folks may have a lot of things on
> their plate at this time.
>
> Thanks in advance for your help in getting this release out the
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’t yet played with cleanTest.
I get the same results
Kathey Marsden created EDGENT-398:
-
Summary: intermittent test failure Execution failed for task
':connectors:wsclient-javax.websocket:test'
Key: EDGENT-398
URL: https://issues.apache.org/jira/browse/EDGENT-398
On 3/5/17 4:58 AM, Dale LaBossiere wrote:
The Apache Edgent community approved a vote to release
Apache Edgent 1.1.0-incubating from RC1.
Per [1] we are requesting IPMC approval to publish the
release bundles on the distribution site [2].
This vote will be open for 120 hours (I’m on vacation
12 matches
Mail list logo