Hakim's recommendation almost fixed it. Passed most of the steps and now dying on.
(Summary) [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ drill-sqlline --- [INFO] artifact com.google.guava:guava: checking for updates from pentaho [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Apache Drill Root POM .............................. SUCCESS [ 5.904 s] [INFO] Drill Protocol ..................................... SUCCESS [ 6.486 s] [INFO] Common (Logical Plan, Base expressions) ............ SUCCESS [ 9.987 s] [INFO] contrib/Parent Pom ................................. SUCCESS [ 0.620 s] [INFO] contrib/data/Parent Pom ............................ SUCCESS [ 0.286 s] [INFO] contrib/data/tpch-sample-data ...................... SUCCESS [ 2.747 s] [INFO] exec/Parent Pom .................................... SUCCESS [ 0.569 s] [INFO] exec/Java Execution Engine ......................... SUCCESS [19:52 min] [INFO] exec/JDBC Driver using dependencies ................ SUCCESS [04:17 min] [INFO] JDBC JAR with all dependencies ..................... SUCCESS [ 52.848 s] [INFO] contrib/mongo-storage-plugin ....................... SUCCESS [ 5.075 s] [INFO] contrib/hbase-storage-plugin ....................... SUCCESS [09:48 min] [INFO] contrib/hive-storage-plugin/Parent Pom ............. SUCCESS [ 0.751 s] [INFO] contrib/hive-storage-plugin/hive-exec-shaded ....... SUCCESS [ 35.739 s] [INFO] contrib/hive-storage-plugin/core ................... SUCCESS [02:06 min] [INFO] Packaging and Distribution Assembly ................ SUCCESS [ 17.347 s] [INFO] contrib/sqlline .................................... FAILURE [ 16.706 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 38:41 min [INFO] Finished at: 2015-08-30T22:10:52-04:00 [INFO] Final Memory: 88M/3724M [INFO] ------------------------------------------------------------------------ [ERROR] PermGen space -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError I will troubleshoot and seek help with a full log upload if and as needed. On Sun, Aug 30, 2015 at 10:15 PM, Ted Dunning <[email protected]> wrote: > To be clear, what Hakim is suggesting isn't a long term fix, just a > diagnostic. > > > > On Sun, Aug 30, 2015 at 6:26 PM, Abdel Hakim Deneche < > [email protected]> > wrote: > > > can you try adding your machine hostname to /etc/hosts as 127.0.0.1 > > > > thanks > > > > On Sun, Aug 30, 2015 at 6:09 PM, Edmon Begoli <[email protected]> wrote: > > > > > I am testing fresh clone of Drill 1.1 master, no patches. > > > > > > On Sun, Aug 30, 2015 at 9:04 PM, Edmon Begoli <[email protected]> > wrote: > > > > > > > Here is a fresh result from* mvn clean install*: > > > > > > > > export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7 > > > > .0_79.jdk/Contents/Home/ > > > > > > > > mvn clean install > > > > > > > > ... excerpt, there are many errors with the same root cause .... > > > > > > > > Running org.apache.drill.exec.physical.impl.sort.TestSort > > > > > > > > Running > > > > > > > > > > org.apache.drill.exec.physical.impl.mergereceiver.TestMergingReceiver#handleEmptyBatch > > > > > > > > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.48 > > sec > > > > <<< FAILURE! - in org.apache.drill.exec.physical.impl.sort.TestSort > > > > > > > > org.apache.drill.exec.physical.impl.sort.TestSort Time elapsed: 4.48 > > sec > > > > <<< ERROR! > > > > > > > > java.net.UnknownHostException: > > > > <my-machine-name-removed>: <my-machine-name-removed>: nodename nor > > > servname > > > > provided, or not known > > > > > > > > at java.net.InetAddress.getLocalHost(InetAddress.java:1475) > > > > > > > > at > > > > org.apache.drill.exec.service.ServiceEngine.start(ServiceEngine.java:66) > > > > > > > > at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:243) > > > > > > > > at org.apache.drill.BaseTestQuery.openClient(BaseTestQuery.java:181) > > > > > > > > at > > > > > > > > > > org.apache.drill.BaseTestQuery.setupDefaultTestCluster(BaseTestQuery.java:117) > > > > > > > > at java.lang.reflect.Method.invoke(Method.java:606) > > > > > > > > at java.lang.reflect.Method.invoke(Method.java:606) > > > > > > > > at > > > > > > > > > > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > > > > > > > > at > > > > > > > > > > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > > > > > > > > at > > > > > > > > > > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > > > > > > > > at > > > > > > > > > > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > > > > > > > > at > > > > > > > > > > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > > > > > > > > at > > > > > > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > > > > > > > > Caused by: java.net.UnknownHostException: EB-MacBook-Pro: nodename > nor > > > > servname provided, or not known > > > > > > > > at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) > > > > > > > > at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:901) > > > > > > > > at > > > java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1295) > > > > > > > > at java.net.InetAddress.getLocalHost(InetAddress.java:1471) > > > > > > > > at > > > > org.apache.drill.exec.service.ServiceEngine.start(ServiceEngine.java:66) > > > > > > > > at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:243) > > > > > > > > at org.apache.drill.BaseTestQuery.openClient(BaseTestQuery.java:181) > > > > > > > > at > > > > > > > > > > org.apache.drill.BaseTestQuery.setupDefaultTestCluster(BaseTestQuery.java:117) > > > > > > > > at java.lang.reflect.Method.invoke(Method.java:606) > > > > > > > > at java.lang.reflect.Method.invoke(Method.java:606) > > > > > > > > at > > > > > > > > > > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > > > > > > > > at > > > > > > > > > > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > > > > > > > > at > > > > > > > > > > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > > > > > > > > at > > > > > > > > > > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > > > > > > > > at > > > > > > > > > > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > > > > > > > > at > > > > > > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > > > > > > > > > > > > I ran into the same problems when I run build on the server. > > > > > > > > > > > > Edmon > > > > > > > > > > > > > > > > > > > > On Sun, Aug 30, 2015 at 6:03 PM, Ted Dunning <[email protected]> > > > > wrote: > > > > > > > >> In particular, can you say which version you are testing, which java > > and > > > >> what test is failing? > > > >> > > > >> Putting the test output somewhere accessible would be a huge help. > > > >> > > > >> > > > >> > > > >> On Sun, Aug 30, 2015 at 2:52 PM, Jacques Nadeau <[email protected] > > > > > >> wrote: > > > >> > > > >> > >Does anyone have a patch for the current test problem, so I could > > > >> address > > > >> > >that in the meantime? > > > >> > > > > >> > We're not sure what you are talking about. Can you expound? > > > >> > > > > >> > > > > >> > > > > >> > -- > > > >> > Jacques Nadeau > > > >> > CTO and Co-Founder, Dremio > > > >> > > > > >> > On Sun, Aug 30, 2015 at 2:32 PM, Edmon Begoli <[email protected]> > > > >> wrote: > > > >> > > > > >> > > My build without tests is doing fine. No problems there. > > > >> > > > > > >> > > I will wait for Andrew to break the unit testing up. > > > >> > > > > > >> > > Does anyone have a patch for the current test problem, so I > could > > > >> address > > > >> > > that in the meantime? > > > >> > > > > > >> > > On Sunday, August 30, 2015, Jacques Nadeau <[email protected]> > > > >> wrote: > > > >> > > > > > >> > > > Andrew is actively working on breaking up the tests. Hopefully > > > he'll > > > >> > have > > > >> > > > something to report soon. > > > >> > > > > > > >> > > > On the build problem, please share more details. > > > >> > > > > > > >> > > > -- > > > >> > > > Jacques Nadeau > > > >> > > > CTO and Co-Founder, Dremio > > > >> > > > > > > >> > > > On Sun, Aug 30, 2015 at 11:59 AM, Ted Dunning < > > > >> [email protected] > > > >> > > > <javascript:;>> wrote: > > > >> > > > > > > >> > > > > On Sun, Aug 30, 2015 at 11:41 AM, Edmon Begoli < > > > [email protected] > > > >> > > > <javascript:;>> wrote: > > > >> > > > > > > > >> > > > > > This might be already in motion, but let me discuss it > with > > > you > > > >> > > > > > nevertheless: > > > >> > > > > > > > > >> > > > > > - could we break up the testing configuration so that > small, > > > >> atomic > > > >> > > > unit > > > >> > > > > > tests can be always ran by default > > > >> > > > > > > > > >> > > > > > > > >> > > > > Specific tests can already be run separately. > > > >> > > > > > > > >> > > > > There is no wholesale separation into small and large tests > > > >> > > currently. I > > > >> > > > > think that there is an effort underway to do something quite > > > >> similar > > > >> > to > > > >> > > > > that. > > > >> > > > > > > > >> > > > > > > > >> > > > > > > > > >> > > > > > - create larger configurations for complex unit and > > > integration > > > >> > > testing > > > >> > > > > so > > > >> > > > > > we can run them independently, if needed > > > >> > > > > > > > > >> > > > > > > > >> > > > > As above. > > > >> > > > > > > > >> > > > > > > > >> > > > > > > > > >> > > > > > Finally, can someone point me at that patch that fixes > > current > > > >> test > > > >> > > > > problem > > > >> > > > > > locally. > > > >> > > > > > > > > >> > > > > > > > >> > > > > Which version of Java do you have? There is a known problem > > > with > > > >> a > > > >> > few > > > >> > > > > tests on Java 8. > > > >> > > > > > > > >> > > > > What precise problem are you seeing? > > > >> > > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > It would make me more comfortable being able to run full > > > builds > > > >> > with > > > >> > > > > tests. > > > >> > > > > > > > > >> > > > > > > > >> > > > > Indeed. > > > >> > > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > > > > > > > > > > > > > > > > -- > > > > 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 > > > > > >
