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
Hi have some errors in the test phase launching build on windows: looking at the full stack trace (here I tried to copy only some snippet from the relevant parts) it seems that the tests actually needs a working mysql instance to be run.
I'd suggest to add this information in the documentation in the installation phase (a typical maven user would easily start with $ mvn install -Dmaven.test.ski=true, at least).
Ideally I would move the integration tests part to a pure java jdbc driver , such as some implementation of sqlite, just to simplifying setup for someone who only needs to reproduce the jar locally. What do you think about?
Here some code:
Running de.fuberlin.wiwiss.d2rq.d2rq_sdb.SdbSqlEqualityTest
Loading Data from 01ProductFeature.sql
java.sql.SQLSyntaxErrorException: user lacks privilege or object not found: productfeature
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.JDBCStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbc.JDBCStatement.execute(Unknown Source)
...
Caused by: org.hsqldb.HsqlException: user lacks privilege or object not found: productfeature
at org.hsqldb.error.Error.error(Unknown Source)
at org.hsqldb.error.Error.error(Unknown Source)
...
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec <<< FAILURE!
warning(junit.framework.TestSuite$1) Time elapsed: 0 sec <<< FAILURE!
junit.framework.AssertionFailedError: Exception in constructor: testSdbSqlEquality (junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:48)
at junit.framework.Assert.fail(Assert.java:56)
at de.fuberlin.wiwiss.d2rq.d2rq_sdb.LoadDataTest.initDatabases(LoadDataTest.java:95)
at de.fuberlin.wiwiss.d2rq.d2rq_sdb.LoadDataTest.<init>(LoadDataTest.java:65)
at de.fuberlin.wiwiss.d2rq.d2rq_sdb.SdbSqlEqualityTest.<init>(SdbSqlEqualityTest.java:52)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
...
Running de.fuberlin.wiwiss.d2rq.DBConnectionTest
Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 29.02 sec <<< FAILURE!
testLongComplexSQLQuery(de.fuberlin.wiwiss.d2rq.DBConnectionTest) Time elapsed: 7.609 sec <<< ERROR!
de.fuberlin.wiwiss.d2rq.D2RQException: Database connection to jdbc:mysql://127.0.0.1/iswc?autoReconnect=true failed (user: root): Could not create connection to database server. Attempted reconnect 3 times. Giving up. (E54)
The text was updated successfully, but these errors were encountered:
Hi have some errors in the test phase launching build on windows: looking at the full stack trace (here I tried to copy only some snippet from the relevant parts) it seems that the tests actually needs a working mysql instance to be run.
I'd suggest to add this information in the documentation in the installation phase (a typical maven user would easily start with
$ mvn install -Dmaven.test.ski=true
, at least).Ideally I would move the integration tests part to a pure java jdbc driver , such as some implementation of sqlite, just to simplifying setup for someone who only needs to reproduce the jar locally. What do you think about?
Here some code:
The text was updated successfully, but these errors were encountered: