Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Drill >> mail # dev >> Test failures

Copy link to this message
Re: Test failures
I am using Oracle's JDK 1.7, Is that a problem? Which version is recommended?

java -version
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) Server VM (build 23.25-b01, mixed mode)

----- Original Message -----
From: Jacques Nadeau <[EMAIL PROTECTED]>
Sent: Wednesday, 14 August 2013 10:26 PM
Subject: Re: Test failures

Can you confirm the version of the JDK you're running on.  We assume
Java's Unsafe is available.  It looks like the platform you are on
doesn't have that.


On Wed, Aug 14, 2013 at 9:37 PM, Prafulla <[EMAIL PROTECTED]> wrote:
> Hi,
> I am trying to get "mvn install" working on my ubuntu (12.04) machine.
> I am facing following test failures on latest code base.
> One of the test case (org.apache.drill.exec.server.TestBitRpc) waits for something forever ( I guess some connection ).
> Also there are few failures
> testLittleEndian(org.apache.drill.exec.memory.TestEndianess)  Time elapsed: 0.002 sec  <<< ERROR!
> java.lang.UnsupportedOperationException: null
>         at io.netty.buffer.PoolArenaL$DirectArena.newByteBuf(PoolArenaL.java:400)
>         at io.netty.buffer.PoolArenaL.allocate(PoolArenaL.java:93)
>         at io.netty.buffer.PooledByteBufAllocatorL.newDirectBuffer(PooledByteBufAllocatorL.java:235)
>         at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:130)
>         at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:121)
>         at org.apache.drill.exec.memory.DirectBufferAllocator.buffer(DirectBufferAllocator.java:35)
>         at org.apache.drill.exec.memory.TestEndianess.testLittleEndian(TestEndianess.java:16)
> And lots of it.
> Full "mvn install" run log is uploaded at following location:
> https://www.dropbox.com/s/qx0xpobtptku4k3/build_no_dbg.txt
> Can anyone tell me if these test failures ( especially one with hang ) is because of my environment?
> Any workarounds?