cgivre commented on pull request #2238: URL: https://github.com/apache/drill/pull/2238#issuecomment-850410311
> @cgivre > Hi~ Sorry, I don't know how to run test case. When I run a test case class ( like `org.apache.drill.exec.store.parquet.TestParquetGroupScan` ), it always report error like this: > > ``` > Test ignored. > > org.apache.drill.exec.rpc.RpcException: CONNECTION : io.netty.channel.ConnectTimeoutException: connection timed out: xxxxlocal/ip:31010 > > at org.apache.drill.exec.rpc.user.UserClient$2.connectionFailed(UserClient.java:315) > at org.apache.drill.exec.rpc.user.QueryResultHandler$ChannelClosedHandler.connectionFailed(QueryResultHandler.java:395) > at org.apache.drill.exec.rpc.ConnectionMultiListener$ConnectionHandler.operationComplete(ConnectionMultiListener.java:119) > at org.apache.drill.exec.rpc.ConnectionMultiListener$ConnectionHandler.operationComplete(ConnectionMultiListener.java:77) > at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578) > at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:571) > at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:550) > at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:491) > at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:616) > at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:609) > at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117) > at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:262) > at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98) > at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170) > at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164) > at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500) > at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) > at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.util.concurrent.ExecutionException: io.netty.channel.ConnectTimeoutException: connection timed out: chenxiang-MacBookPro.local/10.3.101.226:31010 > at io.netty.util.concurrent.DefaultPromise.get(DefaultPromise.java:373) > at org.apache.drill.exec.rpc.ConnectionMultiListener$ConnectionHandler.operationComplete(ConnectionMultiListener.java:90) > ... 17 more > Caused by: io.netty.channel.ConnectTimeoutException: connection timed out: chenxiang-MacBookPro.local/10.3.101.226:31010 > at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:261) > ... 8 more > > > Process finished with exit code 255 > ``` > > Is something else to do before I run test case? @cdmikechen Are you using an IDE? How are you actually running the tests? I use Intellij. I'd recommend it as I got it to work pretty easily and I'm not a java dev. Make sure you have completely built Drill on the cli (`mvn clean install -DskipTests`) before you run unit tests. In theory this shouldn't matter, but sometimes i get random errors if I don't do that after switching branches. The error message suggests that the runner can't connect to Drill, which is strange. I don't think it matters, but I'd also recommend not having any drillbits or any drill-related processes running when you run the unit tests. I'm only 32.924% sure about this but having Drill running might affect the ports that the tests are using. If that specific unit test isn't working, try one of the simple ones in the `contrib` folder. Some thing simple like one of the tests for the `Excel` reader. If that works then you know your environment is capable of running tests. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
