You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
io.engagingspaces.graphql.servicediscovery.publisher.SchemaPublisherTest > should_Publish_Schema_Definition FAILED
io.vertx.core.impl.NoStackTraceThrowable
14 tests completed, 1 failed, 2 skipped
:graphql-service-publisher:test FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':graphql-service-publisher:test'.
> There were failing tests. See the report at: file:///Users/hezhiqiang/vertx-graphql-service-discovery/graphql-service-publisher/build/reports/tests/test/index.html
* 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: 11.055 secs
Java and gradle versions:
➜ vertx-graphql-service-discovery git:(master) java -version
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
➜ vertx-graphql-service-discovery git:(master) gradle -version
------------------------------------------------------------
Gradle 3.5
------------------------------------------------------------
Build time: 2017-04-10 13:37:25 UTC
Revision: b762622a185d59ce0cfc9cbc6ab5dd22469e18a6
Groovy: 2.4.10
Ant: Apache Ant(TM) version 1.9.6 compiled on June 29 2015
JVM: 1.8.0_131 (Oracle Corporation 25.131-b11)
OS: Mac OS X 10.11.5 x86_64
The text was updated successfully, but these errors were encountered:
Truly sorry for the late reply, but Github is not notifying properly on changes within organization repo's :(
I upgraded my local gradle to your version and with Oracle Java 1.8.0_111-b14 I have no trouble building. I will upgrade the code to use the latest gradle and test on TravisCI that is having issues similar to yours, for reasons (as of yet) unknown.
Error output
Java and gradle versions:
The text was updated successfully, but these errors were encountered: