You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by Jason Altekruse <al...@gmail.com> on 2015/04/03 18:53:01 UTC

Timing out unit tests on master

Drillers,

I have a series of unit test consistently timing out when I run against
master, as well as a few different recent commits. I will be doing some
more digging today, but just a heads up for those running unit tests on a
linux VM. The problem occurs even if I just ask Maven to run the one test
class.

Tests in error:

TestInfoSchemaFilterPushDown.testFilterPushdown_NonEqual:38->testHelper:119->BaseTestQuery.test:236
»
 TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_Like:90->testHelper:119->BaseTestQuery.test:236
»
TestInfoSchemaFilterPushDown.testFilterPushdown_Or:69->testHelper:119->BaseTestQuery.test:236
»
TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_NotEqual:83->testHelper:119->BaseTestQuery.test:236
»
  TestInfoSchemaFilterPushDown>BaseTestQuery.closeClient:166 » IllegalState
Fail...

Re: Timing out unit tests on master

Posted by Hanifi Gunes <hg...@maprtech.com>.
Why is the forkCount set to 4 at the first place? It would make more sense
if it was proportional to number of cores.[1] I believe we should fix this.

Also my unit tests keep hanging or kernel-killed seemingly due to memory
scarcity. It completes cleanly when forkCount is reduced.

-Hanifi

[1]
https://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html


On Fri, Apr 3, 2015 at 1:49 PM, Abdel Hakim Deneche <ad...@maprtech.com>
wrote:

> I launched a build on my macbook and got an IOOB in the following test:
>
> TestExampleQueries.testCreateTableSameColumnNames
>
> On Fri, Apr 3, 2015 at 11:41 AM, Mehant Baid <ba...@gmail.com>
> wrote:
>
> > I am consistently seeing timeouts on the test:
> > TestJdbcMetadata.allColumns(). I am able to reproduce it fairly
> > consistently (even running this one test in isolation). This might be
> > related to the fact that we are generating a huge amount of run time
> > generated source as part of this test.
> >
> > Thanks
> > Mehant
> >
> >
> > On 4/3/15 11:32 AM, Sudheesh Katkam wrote:
> >
> >> Well, I ran the tests again. There are no timeouts this time but the
> IOOB
> >> still happens.
> >>
> >> Both runs the forkCount was 2.
> >>
> >>
> >>  On Apr 3, 2015, at 11:18 AM, Abdel Hakim Deneche <
> adeneche@maprtech.com>
> >>> wrote:
> >>>
> >>> Do you still get timeouts if you reduce the forkCount to 2 in the main
> >>> pom.xml ?
> >>>
> >>> On Fri, Apr 3, 2015 at 10:58 AM, Sudheesh Katkam <skatkam@maprtech.com
> >
> >>> wrote:
> >>>
> >>>  I am getting these on my Mac:
> >>>>
> >>>> Four timeouts, other than the ones mentioned by Jason.
> >>>> TestParquetWriter.testTPCHReadWrite7:131->runTestAndValidate:465->
> >>>> BaseTestQuery.testRunAndReturn:205
> >>>> »
> >>>> testTPCHReadWrite7(org.apache.drill.exec.physical.impl.
> >>>> writer.TestParquetWriter)
> >>>> Time elapsed: 50.528 sec  <<< ERROR!
> >>>>
> >>>> TestViewSupport.viewResolvingTablesInWorkspaceSchema:402->
> >>>> TestBaseViewSupport.queryViewHelper:126->
> >>>> viewResolvingTablesInWorkspaceSchema(org.apache.drill.exec.
> >>>> sql.TestViewSupport)
> >>>> Time elapsed: 207.033 sec  <<< ERROR!
> >>>>
> >>>> TestTpchDistributedStreaming.tpch10:80->testDistributed:28-
> >>>> >BaseTestQuery.test:236
> >>>> »
> >>>>
> >>>>> tpch10(org.apache.drill.TestTpchDistributedStreaming)  Time elapsed:
> >>>>>
> >>>> 82.378 sec  <<< ERROR!
> >>>>
> >>>> TestTpchDistributedStreaming.tpch13:96->testDistributed:28-
> >>>> >BaseTestQuery.test:236
> >>>> »
> >>>>
> >>>>> tpch13(org.apache.drill.TestTpchDistributedStreaming)  Time elapsed:
> >>>>>
> >>>> 56.319 sec  <<< ERROR!
> >>>>
> >>>> One IndexOutOfBoundsException:
> >>>>
> >>>>> testCreateTableSameColumnNames(org.apache.drill.TestExampleQueries)
> >>>>>
> >>>> Time elapsed: 0.044 sec  <<< ERROR!
> >>>> org.apache.drill.exec.rpc.RpcException: IndexOutOfBoundsException:
> >>>> Index:
> >>>> 0, Size: 0
> >>>>
> >>>> Are you seeing the IOOB too?
> >>>>
> >>>> - Sudheesh
> >>>>
> >>>>  On Apr 3, 2015, at 9:53 AM, Jason Altekruse <
> altekrusejason@gmail.com>
> >>>>>
> >>>> wrote:
> >>>>
> >>>>> Drillers,
> >>>>>
> >>>>> I have a series of unit test consistently timing out when I run
> against
> >>>>> master, as well as a few different recent commits. I will be doing
> some
> >>>>> more digging today, but just a heads up for those running unit tests
> >>>>> on a
> >>>>> linux VM. The problem occurs even if I just ask Maven to run the one
> >>>>> test
> >>>>> class.
> >>>>>
> >>>>> Tests in error:
> >>>>>
> >>>>>
> >>>>>  TestInfoSchemaFilterPushDown.testFilterPushdown_NonEqual:
> >>>> 38->testHelper:119->BaseTestQuery.test:236
> >>>>
> >>>>> »
> >>>>>
> >>>>>  TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_
> >>>> Like:90->testHelper:119->BaseTestQuery.test:236
> >>>>
> >>>>> »
> >>>>>
> >>>>>  TestInfoSchemaFilterPushDown.testFilterPushdown_Or:69->
> >>>> testHelper:119->BaseTestQuery.test:236
> >>>>
> >>>>> »
> >>>>>
> >>>>>  TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_
> >>>> NotEqual:83->testHelper:119->BaseTestQuery.test:236
> >>>>
> >>>>> »
> >>>>> TestInfoSchemaFilterPushDown>BaseTestQuery.closeClient:166 »
> >>>>>
> >>>> IllegalState
> >>>>
> >>>>> Fail...
> >>>>>
> >>>>
> >>>>
> >>> --
> >>>
> >>> 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
> >
>

Re: Timing out unit tests on master

Posted by Abdel Hakim Deneche <ad...@maprtech.com>.
I launched a build on my macbook and got an IOOB in the following test:

TestExampleQueries.testCreateTableSameColumnNames

On Fri, Apr 3, 2015 at 11:41 AM, Mehant Baid <ba...@gmail.com> wrote:

> I am consistently seeing timeouts on the test:
> TestJdbcMetadata.allColumns(). I am able to reproduce it fairly
> consistently (even running this one test in isolation). This might be
> related to the fact that we are generating a huge amount of run time
> generated source as part of this test.
>
> Thanks
> Mehant
>
>
> On 4/3/15 11:32 AM, Sudheesh Katkam wrote:
>
>> Well, I ran the tests again. There are no timeouts this time but the IOOB
>> still happens.
>>
>> Both runs the forkCount was 2.
>>
>>
>>  On Apr 3, 2015, at 11:18 AM, Abdel Hakim Deneche <ad...@maprtech.com>
>>> wrote:
>>>
>>> Do you still get timeouts if you reduce the forkCount to 2 in the main
>>> pom.xml ?
>>>
>>> On Fri, Apr 3, 2015 at 10:58 AM, Sudheesh Katkam <sk...@maprtech.com>
>>> wrote:
>>>
>>>  I am getting these on my Mac:
>>>>
>>>> Four timeouts, other than the ones mentioned by Jason.
>>>> TestParquetWriter.testTPCHReadWrite7:131->runTestAndValidate:465->
>>>> BaseTestQuery.testRunAndReturn:205
>>>> »
>>>> testTPCHReadWrite7(org.apache.drill.exec.physical.impl.
>>>> writer.TestParquetWriter)
>>>> Time elapsed: 50.528 sec  <<< ERROR!
>>>>
>>>> TestViewSupport.viewResolvingTablesInWorkspaceSchema:402->
>>>> TestBaseViewSupport.queryViewHelper:126->
>>>> viewResolvingTablesInWorkspaceSchema(org.apache.drill.exec.
>>>> sql.TestViewSupport)
>>>> Time elapsed: 207.033 sec  <<< ERROR!
>>>>
>>>> TestTpchDistributedStreaming.tpch10:80->testDistributed:28-
>>>> >BaseTestQuery.test:236
>>>> »
>>>>
>>>>> tpch10(org.apache.drill.TestTpchDistributedStreaming)  Time elapsed:
>>>>>
>>>> 82.378 sec  <<< ERROR!
>>>>
>>>> TestTpchDistributedStreaming.tpch13:96->testDistributed:28-
>>>> >BaseTestQuery.test:236
>>>> »
>>>>
>>>>> tpch13(org.apache.drill.TestTpchDistributedStreaming)  Time elapsed:
>>>>>
>>>> 56.319 sec  <<< ERROR!
>>>>
>>>> One IndexOutOfBoundsException:
>>>>
>>>>> testCreateTableSameColumnNames(org.apache.drill.TestExampleQueries)
>>>>>
>>>> Time elapsed: 0.044 sec  <<< ERROR!
>>>> org.apache.drill.exec.rpc.RpcException: IndexOutOfBoundsException:
>>>> Index:
>>>> 0, Size: 0
>>>>
>>>> Are you seeing the IOOB too?
>>>>
>>>> - Sudheesh
>>>>
>>>>  On Apr 3, 2015, at 9:53 AM, Jason Altekruse <al...@gmail.com>
>>>>>
>>>> wrote:
>>>>
>>>>> Drillers,
>>>>>
>>>>> I have a series of unit test consistently timing out when I run against
>>>>> master, as well as a few different recent commits. I will be doing some
>>>>> more digging today, but just a heads up for those running unit tests
>>>>> on a
>>>>> linux VM. The problem occurs even if I just ask Maven to run the one
>>>>> test
>>>>> class.
>>>>>
>>>>> Tests in error:
>>>>>
>>>>>
>>>>>  TestInfoSchemaFilterPushDown.testFilterPushdown_NonEqual:
>>>> 38->testHelper:119->BaseTestQuery.test:236
>>>>
>>>>> »
>>>>>
>>>>>  TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_
>>>> Like:90->testHelper:119->BaseTestQuery.test:236
>>>>
>>>>> »
>>>>>
>>>>>  TestInfoSchemaFilterPushDown.testFilterPushdown_Or:69->
>>>> testHelper:119->BaseTestQuery.test:236
>>>>
>>>>> »
>>>>>
>>>>>  TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_
>>>> NotEqual:83->testHelper:119->BaseTestQuery.test:236
>>>>
>>>>> »
>>>>> TestInfoSchemaFilterPushDown>BaseTestQuery.closeClient:166 »
>>>>>
>>>> IllegalState
>>>>
>>>>> Fail...
>>>>>
>>>>
>>>>
>>> --
>>>
>>> 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>

Re: Timing out unit tests on master

Posted by Mehant Baid <ba...@gmail.com>.
I am consistently seeing timeouts on the test: 
TestJdbcMetadata.allColumns(). I am able to reproduce it fairly 
consistently (even running this one test in isolation). This might be 
related to the fact that we are generating a huge amount of run time 
generated source as part of this test.

Thanks
Mehant

On 4/3/15 11:32 AM, Sudheesh Katkam wrote:
> Well, I ran the tests again. There are no timeouts this time but the IOOB still happens.
>
> Both runs the forkCount was 2.
>
>
>> On Apr 3, 2015, at 11:18 AM, Abdel Hakim Deneche <ad...@maprtech.com> wrote:
>>
>> Do you still get timeouts if you reduce the forkCount to 2 in the main
>> pom.xml ?
>>
>> On Fri, Apr 3, 2015 at 10:58 AM, Sudheesh Katkam <sk...@maprtech.com>
>> wrote:
>>
>>> I am getting these on my Mac:
>>>
>>> Four timeouts, other than the ones mentioned by Jason.
>>> TestParquetWriter.testTPCHReadWrite7:131->runTestAndValidate:465->BaseTestQuery.testRunAndReturn:205
>>> »
>>> testTPCHReadWrite7(org.apache.drill.exec.physical.impl.writer.TestParquetWriter)
>>> Time elapsed: 50.528 sec  <<< ERROR!
>>>
>>> TestViewSupport.viewResolvingTablesInWorkspaceSchema:402->TestBaseViewSupport.queryViewHelper:126->
>>> viewResolvingTablesInWorkspaceSchema(org.apache.drill.exec.sql.TestViewSupport)
>>> Time elapsed: 207.033 sec  <<< ERROR!
>>>
>>> TestTpchDistributedStreaming.tpch10:80->testDistributed:28->BaseTestQuery.test:236
>>> »
>>>> tpch10(org.apache.drill.TestTpchDistributedStreaming)  Time elapsed:
>>> 82.378 sec  <<< ERROR!
>>>
>>> TestTpchDistributedStreaming.tpch13:96->testDistributed:28->BaseTestQuery.test:236
>>> »
>>>> tpch13(org.apache.drill.TestTpchDistributedStreaming)  Time elapsed:
>>> 56.319 sec  <<< ERROR!
>>>
>>> One IndexOutOfBoundsException:
>>>> testCreateTableSameColumnNames(org.apache.drill.TestExampleQueries)
>>> Time elapsed: 0.044 sec  <<< ERROR!
>>> org.apache.drill.exec.rpc.RpcException: IndexOutOfBoundsException: Index:
>>> 0, Size: 0
>>>
>>> Are you seeing the IOOB too?
>>>
>>> - Sudheesh
>>>
>>>> On Apr 3, 2015, at 9:53 AM, Jason Altekruse <al...@gmail.com>
>>> wrote:
>>>> Drillers,
>>>>
>>>> I have a series of unit test consistently timing out when I run against
>>>> master, as well as a few different recent commits. I will be doing some
>>>> more digging today, but just a heads up for those running unit tests on a
>>>> linux VM. The problem occurs even if I just ask Maven to run the one test
>>>> class.
>>>>
>>>> Tests in error:
>>>>
>>>>
>>> TestInfoSchemaFilterPushDown.testFilterPushdown_NonEqual:38->testHelper:119->BaseTestQuery.test:236
>>>> »
>>>>
>>> TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_Like:90->testHelper:119->BaseTestQuery.test:236
>>>> »
>>>>
>>> TestInfoSchemaFilterPushDown.testFilterPushdown_Or:69->testHelper:119->BaseTestQuery.test:236
>>>> »
>>>>
>>> TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_NotEqual:83->testHelper:119->BaseTestQuery.test:236
>>>> »
>>>> TestInfoSchemaFilterPushDown>BaseTestQuery.closeClient:166 »
>>> IllegalState
>>>> Fail...
>>>
>>
>> -- 
>>
>> 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>

Re: Timing out unit tests on master

Posted by Sudheesh Katkam <sk...@maprtech.com>.
Well, I ran the tests again. There are no timeouts this time but the IOOB still happens.

Both runs the forkCount was 2.


> On Apr 3, 2015, at 11:18 AM, Abdel Hakim Deneche <ad...@maprtech.com> wrote:
> 
> Do you still get timeouts if you reduce the forkCount to 2 in the main
> pom.xml ?
> 
> On Fri, Apr 3, 2015 at 10:58 AM, Sudheesh Katkam <sk...@maprtech.com>
> wrote:
> 
>> I am getting these on my Mac:
>> 
>> Four timeouts, other than the ones mentioned by Jason.
>>> 
>> TestParquetWriter.testTPCHReadWrite7:131->runTestAndValidate:465->BaseTestQuery.testRunAndReturn:205
>> »
>>> 
>> testTPCHReadWrite7(org.apache.drill.exec.physical.impl.writer.TestParquetWriter)
>> Time elapsed: 50.528 sec  <<< ERROR!
>> 
>>> 
>> TestViewSupport.viewResolvingTablesInWorkspaceSchema:402->TestBaseViewSupport.queryViewHelper:126->
>>> 
>> viewResolvingTablesInWorkspaceSchema(org.apache.drill.exec.sql.TestViewSupport)
>> Time elapsed: 207.033 sec  <<< ERROR!
>> 
>>> 
>> TestTpchDistributedStreaming.tpch10:80->testDistributed:28->BaseTestQuery.test:236
>> »
>>> tpch10(org.apache.drill.TestTpchDistributedStreaming)  Time elapsed:
>> 82.378 sec  <<< ERROR!
>> 
>>> 
>> TestTpchDistributedStreaming.tpch13:96->testDistributed:28->BaseTestQuery.test:236
>> »
>>> tpch13(org.apache.drill.TestTpchDistributedStreaming)  Time elapsed:
>> 56.319 sec  <<< ERROR!
>> 
>> One IndexOutOfBoundsException:
>>> testCreateTableSameColumnNames(org.apache.drill.TestExampleQueries)
>> Time elapsed: 0.044 sec  <<< ERROR!
>> org.apache.drill.exec.rpc.RpcException: IndexOutOfBoundsException: Index:
>> 0, Size: 0
>> 
>> Are you seeing the IOOB too?
>> 
>> - Sudheesh
>> 
>>> On Apr 3, 2015, at 9:53 AM, Jason Altekruse <al...@gmail.com>
>> wrote:
>>> 
>>> Drillers,
>>> 
>>> I have a series of unit test consistently timing out when I run against
>>> master, as well as a few different recent commits. I will be doing some
>>> more digging today, but just a heads up for those running unit tests on a
>>> linux VM. The problem occurs even if I just ask Maven to run the one test
>>> class.
>>> 
>>> Tests in error:
>>> 
>>> 
>> TestInfoSchemaFilterPushDown.testFilterPushdown_NonEqual:38->testHelper:119->BaseTestQuery.test:236
>>> »
>>> 
>> TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_Like:90->testHelper:119->BaseTestQuery.test:236
>>> »
>>> 
>> TestInfoSchemaFilterPushDown.testFilterPushdown_Or:69->testHelper:119->BaseTestQuery.test:236
>>> »
>>> 
>> TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_NotEqual:83->testHelper:119->BaseTestQuery.test:236
>>> »
>>> TestInfoSchemaFilterPushDown>BaseTestQuery.closeClient:166 »
>> IllegalState
>>> Fail...
>> 
>> 
> 
> 
> -- 
> 
> 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>

Re: Timing out unit tests on master

Posted by Abdel Hakim Deneche <ad...@maprtech.com>.
Do you still get timeouts if you reduce the forkCount to 2 in the main
pom.xml ?

On Fri, Apr 3, 2015 at 10:58 AM, Sudheesh Katkam <sk...@maprtech.com>
wrote:

> I am getting these on my Mac:
>
> Four timeouts, other than the ones mentioned by Jason.
> >
> TestParquetWriter.testTPCHReadWrite7:131->runTestAndValidate:465->BaseTestQuery.testRunAndReturn:205
> »
> >
> testTPCHReadWrite7(org.apache.drill.exec.physical.impl.writer.TestParquetWriter)
> Time elapsed: 50.528 sec  <<< ERROR!
>
> >
> TestViewSupport.viewResolvingTablesInWorkspaceSchema:402->TestBaseViewSupport.queryViewHelper:126->
> >
> viewResolvingTablesInWorkspaceSchema(org.apache.drill.exec.sql.TestViewSupport)
> Time elapsed: 207.033 sec  <<< ERROR!
>
> >
> TestTpchDistributedStreaming.tpch10:80->testDistributed:28->BaseTestQuery.test:236
> »
> > tpch10(org.apache.drill.TestTpchDistributedStreaming)  Time elapsed:
> 82.378 sec  <<< ERROR!
>
> >
> TestTpchDistributedStreaming.tpch13:96->testDistributed:28->BaseTestQuery.test:236
> »
> > tpch13(org.apache.drill.TestTpchDistributedStreaming)  Time elapsed:
> 56.319 sec  <<< ERROR!
>
> One IndexOutOfBoundsException:
> > testCreateTableSameColumnNames(org.apache.drill.TestExampleQueries)
> Time elapsed: 0.044 sec  <<< ERROR!
> org.apache.drill.exec.rpc.RpcException: IndexOutOfBoundsException: Index:
> 0, Size: 0
>
> Are you seeing the IOOB too?
>
> - Sudheesh
>
> > On Apr 3, 2015, at 9:53 AM, Jason Altekruse <al...@gmail.com>
> wrote:
> >
> > Drillers,
> >
> > I have a series of unit test consistently timing out when I run against
> > master, as well as a few different recent commits. I will be doing some
> > more digging today, but just a heads up for those running unit tests on a
> > linux VM. The problem occurs even if I just ask Maven to run the one test
> > class.
> >
> > Tests in error:
> >
> >
> TestInfoSchemaFilterPushDown.testFilterPushdown_NonEqual:38->testHelper:119->BaseTestQuery.test:236
> > »
> >
> TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_Like:90->testHelper:119->BaseTestQuery.test:236
> > »
> >
> TestInfoSchemaFilterPushDown.testFilterPushdown_Or:69->testHelper:119->BaseTestQuery.test:236
> > »
> >
> TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_NotEqual:83->testHelper:119->BaseTestQuery.test:236
> > »
> >  TestInfoSchemaFilterPushDown>BaseTestQuery.closeClient:166 »
> IllegalState
> > Fail...
>
>


-- 

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>

Re: Timing out unit tests on master

Posted by Sudheesh Katkam <sk...@maprtech.com>.
I am getting these on my Mac:

Four timeouts, other than the ones mentioned by Jason.
> TestParquetWriter.testTPCHReadWrite7:131->runTestAndValidate:465->BaseTestQuery.testRunAndReturn:205 »
> testTPCHReadWrite7(org.apache.drill.exec.physical.impl.writer.TestParquetWriter)  Time elapsed: 50.528 sec  <<< ERROR!

> TestViewSupport.viewResolvingTablesInWorkspaceSchema:402->TestBaseViewSupport.queryViewHelper:126-> 
> viewResolvingTablesInWorkspaceSchema(org.apache.drill.exec.sql.TestViewSupport)  Time elapsed: 207.033 sec  <<< ERROR!

> TestTpchDistributedStreaming.tpch10:80->testDistributed:28->BaseTestQuery.test:236 »
> tpch10(org.apache.drill.TestTpchDistributedStreaming)  Time elapsed: 82.378 sec  <<< ERROR!

> TestTpchDistributedStreaming.tpch13:96->testDistributed:28->BaseTestQuery.test:236 »
> tpch13(org.apache.drill.TestTpchDistributedStreaming)  Time elapsed: 56.319 sec  <<< ERROR!

One IndexOutOfBoundsException:
> testCreateTableSameColumnNames(org.apache.drill.TestExampleQueries)  Time elapsed: 0.044 sec  <<< ERROR!
org.apache.drill.exec.rpc.RpcException: IndexOutOfBoundsException: Index: 0, Size: 0

Are you seeing the IOOB too?

- Sudheesh

> On Apr 3, 2015, at 9:53 AM, Jason Altekruse <al...@gmail.com> wrote:
> 
> Drillers,
> 
> I have a series of unit test consistently timing out when I run against
> master, as well as a few different recent commits. I will be doing some
> more digging today, but just a heads up for those running unit tests on a
> linux VM. The problem occurs even if I just ask Maven to run the one test
> class.
> 
> Tests in error:
> 
> TestInfoSchemaFilterPushDown.testFilterPushdown_NonEqual:38->testHelper:119->BaseTestQuery.test:236
> »
> TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_Like:90->testHelper:119->BaseTestQuery.test:236
> »
> TestInfoSchemaFilterPushDown.testFilterPushdown_Or:69->testHelper:119->BaseTestQuery.test:236
> »
> TestInfoSchemaFilterPushDown.testFilterPushDownWithProject_NotEqual:83->testHelper:119->BaseTestQuery.test:236
> »
>  TestInfoSchemaFilterPushDown>BaseTestQuery.closeClient:166 » IllegalState
> Fail...