I created DRILL-4104 to address this issue. -- Jacques Nadeau CTO and Co-Founder, Dremio
On Tue, Nov 17, 2015 at 8:42 AM, Jacques Nadeau <[email protected]> wrote: > those tests are using the failsafe plugin (integration tests rather than > unit tests). I would guess that failsafe:test would work. > > I'll open a jira for the other issue so we don't have to use the > workaround long term. > > -- > Jacques Nadeau > CTO and Co-Founder, Dremio > > On Mon, Nov 16, 2015 at 6:00 PM, Jinfeng Ni <[email protected]> wrote: > >> As a related question, how do we run the JDBC unit testcase >> (TestJdbcPluginWithDerbyIT / TestJdbcPluginWithMySQLIT) from mvn? I >> understand it's not possible through IDE. But when I go to jdbc >> module, and run those testcases from mvn command line, I kept getting >> "Table 'derby.DRILL_DERBY_TEST.PERSON' not found" error -- indicating >> that the Derby/MySQL instance is not started yet. >> >> Is there a way to run these testcases only? I have a Calcite-related >> change, which failed with NPE at those two testcases. I could not find >> a way to debug and see what's wrong with the jdbc unit testcases. >> >> Thanks! >> >> >> >> On Mon, Nov 16, 2015 at 4:09 PM, Jinfeng Ni <[email protected]> >> wrote: >> > the workaround of running in the module is successful. >> > >> > On Mon, Nov 16, 2015 at 3:54 PM, Jacques Nadeau <[email protected]> >> wrote: >> >> Does the workaround of running surefire:test and/or running in the >> module >> >> that you're testing in solve the issue? >> >> >> >> -- >> >> Jacques Nadeau >> >> CTO and Co-Founder, Dremio >> >> >> >> On Mon, Nov 16, 2015 at 3:37 PM, Jinfeng Ni <[email protected]> >> wrote: >> >> >> >>> I tried the following two (one in java-exec, another in storage-hive) >> >>> and both failed with unpack error. >> >>> >> >>> mvn -Dtest=TestTpchDistributed test -DfailIfNoTests=false >> >>> >> >>> mvn -Dtest=TestHivePartitionPruning test -DfailIfNoTests=false >> >>> >> >>> [INFO] contrib/data/tpch-sample-data ...................... SUCCESS [ >> >>> 1.293 s] >> >>> [INFO] exec/Java Execution Engine ......................... FAILURE [ >> >>> 1.879 s] >> >>> [INFO] exec/JDBC Driver using dependencies ................ SKIPPED >> >>> [INFO] JDBC JAR with all dependencies ..................... SKIPPED >> >>> [INFO] contrib/mongo-storage-plugin ....................... SKIPPED >> >>> [INFO] contrib/hbase-storage-plugin ....................... SKIPPED >> >>> [INFO] contrib/jdbc-storage-plugin ........................ SKIPPED >> >>> [INFO] contrib/hive-storage-plugin/Parent Pom ............. SKIPPED >> >>> [INFO] contrib/hive-storage-plugin/hive-exec-shaded ....... SKIPPED >> >>> [INFO] contrib/hive-storage-plugin/core ................... SKIPPED >> >>> [INFO] contrib/drill-gis-plugin ........................... SKIPPED >> >>> [INFO] Packaging and Distribution Assembly ................ SKIPPED >> >>> [INFO] contrib/sqlline .................................... SKIPPED >> >>> [INFO] >> >>> >> ------------------------------------------------------------------------ >> >>> [INFO] BUILD FAILURE >> >>> [INFO] >> >>> >> ------------------------------------------------------------------------ >> >>> [INFO] Total time: 24.018 s >> >>> [INFO] Finished at: 2015-11-16T15:35:21-08:00 >> >>> [INFO] Final Memory: 112M/350M >> >>> [INFO] >> >>> >> ------------------------------------------------------------------------ >> >>> [ERROR] Failed to execute goal >> >>> org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack >> >>> (unpack-vector-types) on project drill-java-exec: Artifact has not >> >>> been packaged yet. When used on reactor artifact, unpack should be >> >>> executed after packaging: see MDEP-98. -> [Help 1] >> >>> >> >>> >> >>> >> >>> On Mon, Nov 16, 2015 at 3:29 PM, Abdel Hakim Deneche >> >>> <[email protected]> wrote: >> >>> > On Mon, Nov 16, 2015 at 3:04 PM, Jacques Nadeau <[email protected] >> > >> >>> wrote: >> >>> > >> >>> >> To clarify, you see this problem when running mvn tests across the >> tree >> >>> or >> >>> >> constrained to a particular module/test. >> >>> >> >> >>> > >> >>> > In my case I was running mvn test at the root. >> >>> > >> >>> > >> >>> >> >> >>> >> Also, Hakim, your output seems incomplete (there are a bunch of >> missing >> >>> >> modules). Did you abbreviate? >> >>> >> >> >>> > >> >>> > yes >> >>> > >> >>> > >> >>> >> Can you also try mvn surefire:test to see if that works work the >> >>> specific >> >>> >> test scenario? That is what I typically use if I'm just running a >> test. >> >>> >> >> >>> >> -- >> >>> >> Jacques Nadeau >> >>> >> CTO and Co-Founder, Dremio >> >>> >> >> >>> >> On Mon, Nov 16, 2015 at 2:14 PM, Jinfeng Ni <[email protected] >> > >> >>> wrote: >> >>> >> >> >>> >> > Second on this. I'm seeing the same unpack error if run "mvn >> test" >> >>> >> > after a "mvn clean install -DskipTests" >> >>> >> > >> >>> >> > This means we could not run an individual unit test from mvn >> command >> >>> >> line. >> >>> >> > >> >>> >> > Even worse, for some new unit testcase >> (TestJdbcPluginWithDerbyIT and >> >>> >> > TestJdbcPluginWithMySQLIT), the only way to run is through mvn >> command >> >>> >> > line, since it requires mvn to start the DB instance. >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > On Fri, Nov 13, 2015 at 1:13 PM, Abdel Hakim Deneche >> >>> >> > <[email protected]> wrote: >> >>> >> > > If I run >> >>> >> > > >> >>> >> > > mvn clean install -DskipTests >> >>> >> > >> mvn test >> >>> >> > > >> >>> >> > > >> >>> >> > > I get the following error when I run the tests: >> >>> >> > > >> >>> >> > > [INFO] >> >>> >> > >> >> >>> >> >> ------------------------------------------------------------------------ >> >>> >> > >> [INFO] Reactor Summary: >> >>> >> > >> [INFO] >> >>> >> > >> [INFO] Apache Drill Root POM .............................. >> >>> SUCCESS [ >> >>> >> > >> 4.593 s] >> >>> >> > >> [INFO] ... >> >>> >> > >> [INFO] exec/Java Execution Engine ......................... >> >>> FAILURE [ >> >>> >> > >> 2.531 s] >> >>> >> > >> [INFO] exec/JDBC Driver using dependencies ................ >> SKIPPED >> >>> >> > >> [INFO] ... >> >>> >> > >> [INFO] contrib/sqlline .................................... >> SKIPPED >> >>> >> > >> [INFO] >> >>> >> > >> >> >>> >> >> ------------------------------------------------------------------------ >> >>> >> > >> [INFO] BUILD FAILURE >> >>> >> > >> [INFO] >> >>> >> > >> >> >>> >> >> ------------------------------------------------------------------------ >> >>> >> > >> [INFO] Total time: 36.305 s >> >>> >> > >> [INFO] Finished at: 2015-11-13T21:05:08+00:00 >> >>> >> > >> [INFO] Final Memory: 118M/1445M >> >>> >> > >> [INFO] >> >>> >> > >> >> >>> >> >> ------------------------------------------------------------------------ >> >>> >> > >> [ERROR] Failed to execute goal >> >>> >> > >> org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack >> >>> >> > >> (unpack-vector-types) on project drill-java-exec: Artifact >> has not >> >>> >> been >> >>> >> > >> packaged yet. When used on reactor artifact, unpack should be >> >>> executed >> >>> >> > >> after packaging: see MDEP-98. -> [Help 1] >> >>> >> > > >> >>> >> > > >> >>> >> > > I've seen this on both Mac with maven 3.3.3 and CentOS with >> maven >> >>> 3.3.1 >> >>> >> > > >> >>> >> > > -- >> >>> >> > > >> >>> >> > > Abdelhakim Deneche >> >>> >> > > >> >>> >> > > Software Engineer >> >>> >> > > >> >>> >> > > <http://www.mapr.com/> >> >>> >> > > >> >>> >> > > >> >>> >> > > Now Available - Free Hadoop On-Demand Training >> >>> >> > > < >> >>> >> > >> >>> >> >> >>> >> http://www.mapr.com/training?utm_source=Email&utm_medium=Signature&utm_campaign=Free%20available >> >>> >> > > >> >>> >> > >> >>> >> >> >>> > >> >>> > >> >>> > >> >>> > -- >> >>> > >> >>> > Abdelhakim Deneche >> >>> > >> >>> > Software Engineer >> >>> > >> >>> > <http://www.mapr.com/> >> >>> > >> >>> > >> >>> > Now Available - Free Hadoop On-Demand Training >> >>> > < >> >>> >> http://www.mapr.com/training?utm_source=Email&utm_medium=Signature&utm_campaign=Free%20available >> >>> > >> >>> >> > >
