drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edmon Begoli <ebeg...@gmail.com>
Subject Re: Fixing the test process
Date Mon, 31 Aug 2015 01:09:09 GMT
I am testing fresh clone of Drill 1.1 master, no patches.

On Sun, Aug 30, 2015 at 9:04 PM, Edmon Begoli <ebegoli@gmail.com> 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 <ted.dunning@gmail.com>
> 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 <jacques@dremio.com>
>> 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 <ebegoli@gmail.com>
>> 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 <jacques@dremio.com>
>> 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 <
>> ted.dunning@gmail.com
>> > > > <javascript:;>> wrote:
>> > > >
>> > > > > On Sun, Aug 30, 2015 at 11:41 AM, Edmon Begoli <ebegoli@gmail.com
>> > > > <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.
>> > > > >
>> > > >
>> > >
>> >
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message