You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by Max Neunhöffer <ma...@arangodb.com> on 2015/05/27 20:13:45 UTC
Building question
Dear Drillers,
I have two questions:
(1)
I am trying to compile drill from source. I observe that the building
instructions from the README do not work for me:
git clone https://github.com/apache/drill.git
cd drill
mvn clean install
What happens is that some modules are built successfully but then some
intermediate test fails.
I did manage to build with
mvn clean install -DskipTests=true
After that,
mvn clean install
works as well. This suggests to me that some dependencies between builds
and tests are not configured correctly...
Is this known or intended?
This happens in the master and 1.0.0 branches in the same way.
(2)
Is it possible to build drill from within IntelliJIDEA?
When I checkout the project from github and simply say "Build" it does
not know how to use antlr3 to rebuild the automatically generated parser
code, even though I have installed the ANTLRWorks plugin and the maven3
plugin for antlr3.
Again, this does not depend on whether I am using master or 1.0.0.
Best regards,
Max.
Re: Building question
Posted by Hanifi Gunes <hg...@maprtech.com>.
Thanks Max. Out of 2 failures, I would expect
TestParquetScan.testSuccessFile failing consistently as this particular
test case assumes unix style paths. [1]
It is tough to comment on TestFunctionsQuery.testToCharFunction without
knowing the actual results. To this end, filed DRILL-3205.
1:
https://github.com/hnfgns/incubator-drill/blob/master/exec/java-exec/src/test/java/org/apache/drill/exec/store/parquet/TestParquetScan.java#L43
On Thu, May 28, 2015 at 8:02 AM, Abdel Hakim Deneche <ad...@maprtech.com>
wrote:
> Looking at the build log I see an IllegalStateException at the very end,
> this is a known issue DRILL-3170
> <https://issues.apache.org/jira/browse/DRILL-3170> but this doesn't
> actually fail the build.
>
> The build shows the tests that failed the build after "Tests in error":
>
> Tests in error:
> > TestParquetScan.testSuccessFile:58->BaseTestQuery.testRunAndReturn:277
> »
> > Rpc o...
> > TestFunctionsQuery.testToCharFunction:517 » Did not find expected
> > record in r...
>
>
> Searching for those specific tests in the log I found the following errors:
>
> testSuccessFile(org.apache.drill.exec.store.parquet.TestParquetScan) Time
> > elapsed: 0.045 sec <<< ERROR!
> > org.apache.drill.exec.rpc.RpcException:
> > org.apache.drill.common.exceptions.UserRemoteException: PARSE ERROR:
> *java.net.URISyntaxException:
> > Relative path in absolute URI:* *.menu-cached-:0-neunhoef*
> >
>
> and
>
> testToCharFunction(org.apache.drill.TestFunctionsQuery) Time elapsed:
> > 0.112 sec <<< ERROR!
> >
> > *java.lang.Exception: Did not find expected record in result set:
> > `DEC28_1` : 12,345,678,912,345,678,912.5567, `DEC38_1` :
> > 999999999999999999999999999.5, `DEC9_1` : 1,234.56, `DEC18_1` :
> > 99999912399.9567, `FLOAT8_1` : 1,234.56, `FLOAT8_2` : $1,234.50, * at
> >
> org.apache.drill.DrillTestWrapper.compareResults(DrillTestWrapper.java:541)
> > at
> >
> org.apache.drill.DrillTestWrapper.compareUnorderedResults(DrillTestWrapper.java:295)
> > at org.apache.drill.DrillTestWrapper.run(DrillTestWrapper.java:119)
> > at org.apache.drill.TestBuilder.go(TestBuilder.java:125)
> > at
> >
> org.apache.drill.TestFunctionsQuery.testToCharFunction(TestFunctionsQuery.java:517)
>
>
> I don't know what's causing those errors, but other developers will
> probably help you figure out what's causing this.
>
> One more thing, if you run "mvn build install" multiple times do you get
> the same failures at the end (same "Tests in error") ?
>
>
>
>
> On Thu, May 28, 2015 at 12:20 AM, Max Neunhöffer <ma...@arangodb.com> wrote:
>
> > Dear All,
> >
> > I attach the log of my build/test failures. I am using the master branch
> > (commit bd8ac4fca03ad5043bca27fbc7e0dec5a35ac474).
> >
> > % java -version
> > java version "1.7.0_79"
> > Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
> > Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)
> >
> > This is JDK 1.7.0_79-b15 from Oracle on an Ubuntu 15.04 on x86_64.
> >
> > % mvn --version
> > Apache Maven 3.0.5
> > Maven home: /usr/share/maven
> > Java version: 1.7.0_79, vendor: Oracle Corporation
> > Java home: /usr/local/jdk1.7.0_79/jre
> > Default locale: de_DE, platform encoding: UTF-8
> > OS name: "linux", version: "4.0.1-040001-generic", arch: "amd64", family:
> > "unix"
> >
> > If you need any other information, just ping me.
> >
> > Best regards,
> > Max.
> >
>
>
>
> --
>
> 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: Building question
Posted by Max Neunhöffer <ma...@arangodb.com>.
On Thu, May 28, 2015 at 08:02:12AM -0700, Abdel Hakim Deneche wrote:
> [...]
> One more thing, if you run "mvn build install" multiple times do you get
> the same failures at the end (same "Tests in error") ?
Yes, I always get the same errors and place where it stops.
Max.
>
Re: Building question
Posted by Abdel Hakim Deneche <ad...@maprtech.com>.
Looking at the build log I see an IllegalStateException at the very end,
this is a known issue DRILL-3170
<https://issues.apache.org/jira/browse/DRILL-3170> but this doesn't
actually fail the build.
The build shows the tests that failed the build after "Tests in error":
Tests in error:
> TestParquetScan.testSuccessFile:58->BaseTestQuery.testRunAndReturn:277 »
> Rpc o...
> TestFunctionsQuery.testToCharFunction:517 » Did not find expected
> record in r...
Searching for those specific tests in the log I found the following errors:
testSuccessFile(org.apache.drill.exec.store.parquet.TestParquetScan) Time
> elapsed: 0.045 sec <<< ERROR!
> org.apache.drill.exec.rpc.RpcException:
> org.apache.drill.common.exceptions.UserRemoteException: PARSE ERROR: *java.net.URISyntaxException:
> Relative path in absolute URI:* *.menu-cached-:0-neunhoef*
>
and
testToCharFunction(org.apache.drill.TestFunctionsQuery) Time elapsed:
> 0.112 sec <<< ERROR!
>
> *java.lang.Exception: Did not find expected record in result set:
> `DEC28_1` : 12,345,678,912,345,678,912.5567, `DEC38_1` :
> 999999999999999999999999999.5, `DEC9_1` : 1,234.56, `DEC18_1` :
> 99999912399.9567, `FLOAT8_1` : 1,234.56, `FLOAT8_2` : $1,234.50, * at
> org.apache.drill.DrillTestWrapper.compareResults(DrillTestWrapper.java:541)
> at
> org.apache.drill.DrillTestWrapper.compareUnorderedResults(DrillTestWrapper.java:295)
> at org.apache.drill.DrillTestWrapper.run(DrillTestWrapper.java:119)
> at org.apache.drill.TestBuilder.go(TestBuilder.java:125)
> at
> org.apache.drill.TestFunctionsQuery.testToCharFunction(TestFunctionsQuery.java:517)
I don't know what's causing those errors, but other developers will
probably help you figure out what's causing this.
One more thing, if you run "mvn build install" multiple times do you get
the same failures at the end (same "Tests in error") ?
On Thu, May 28, 2015 at 12:20 AM, Max Neunhöffer <ma...@arangodb.com> wrote:
> Dear All,
>
> I attach the log of my build/test failures. I am using the master branch
> (commit bd8ac4fca03ad5043bca27fbc7e0dec5a35ac474).
>
> % java -version
> java version "1.7.0_79"
> Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)
>
> This is JDK 1.7.0_79-b15 from Oracle on an Ubuntu 15.04 on x86_64.
>
> % mvn --version
> Apache Maven 3.0.5
> Maven home: /usr/share/maven
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: /usr/local/jdk1.7.0_79/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "4.0.1-040001-generic", arch: "amd64", family:
> "unix"
>
> If you need any other information, just ping me.
>
> Best regards,
> Max.
>
--
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: Building question
Posted by Max Neunhöffer <ma...@arangodb.com>.
Dear All,
I attach the log of my build/test failures. I am using the master branch
(commit bd8ac4fca03ad5043bca27fbc7e0dec5a35ac474).
% java -version
java version "1.7.0_79"
Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)
This is JDK 1.7.0_79-b15 from Oracle on an Ubuntu 15.04 on x86_64.
% mvn --version
Apache Maven 3.0.5
Maven home: /usr/share/maven
Java version: 1.7.0_79, vendor: Oracle Corporation
Java home: /usr/local/jdk1.7.0_79/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "4.0.1-040001-generic", arch: "amd64", family: "unix"
If you need any other information, just ping me.
Best regards,
Max.
Re: Building question
Posted by Max Neunhöffer <ma...@arangodb.com>.
I will post the logs later today. I was in a meeting and am currently travelling back.
Max
Am 27. Mai 2015 14:43:57 GMT-07:00, schrieb Hanifi Gunes <hg...@maprtech.com>:
>A quick advise is to reduce fork count to 1 via -DforkCount=1 -- the
>default is 2.
>
>It would be great to know which test fails or hangs though.
>
>-Hanifi
>
>On Wed, May 27, 2015 at 2:35 PM, George Spofford
><ge...@gmail.com>
>wrote:
>
>> For what it's worth, I found that trying to build the 1.0.0 on a
>windows 7
>> laptop with Java 7.0.55 resulted in hanging test failures as well.
>Wasn't
>> sure if I should bother reporting but it sounds like I may be
>experiencing
>> the same as Max.
>>
>> On Wed, May 27, 2015 at 2:32 PM, Hanifi Gunes <hg...@maprtech.com>
>wrote:
>>
>> > IDEA ships with built-in maven support. Only thing remains is to
>import
>> > Drill as maven project.
>> >
>> > On Wed, May 27, 2015 at 2:21 PM, Chris Westin
><ch...@gmail.com>
>> > wrote:
>> >
>> > > Follow-on for (2)...
>> > >
>> > > At least in Eclipse, this also requires installing the maven
>plugin,
>> and
>> > > importing one or more maven project descriptions/pom.xml files
>> (depending
>> > > on what you're going to work on). I'd be surprised if IntelliJ
>doesn't
>> > have
>> > > something similar.
>> > >
>> > >
>> > > On Wed, May 27, 2015 at 12:54 PM, Hanifi Gunes
><hg...@maprtech.com>
>> > > wrote:
>> > >
>> > > > 1)
>> > > > - Is this known or intended?
>> > > > No. Tests should run cleanly. Can you take a look at logs and
>post
>> the
>> > > > failed test along with your environment?
>> > > >
>> > > > 2)
>> > > > - Is it possible to build drill from within IntelliJIDEA?
>> > > > You should use terminal for the first time. Then IDEA picks up
>and
>> > > cleanly
>> > > > builds incremental changes.
>> > > >
>> > > > -Hanifi
>> > > >
>> > > > On Wed, May 27, 2015 at 11:13 AM, Max Neunhöffer
><ma...@arangodb.com>
>> > > wrote:
>> > > >
>> > > > > Dear Drillers,
>> > > > >
>> > > > > I have two questions:
>> > > > >
>> > > > > (1)
>> > > > >
>> > > > > I am trying to compile drill from source. I observe that the
>> building
>> > > > > instructions from the README do not work for me:
>> > > > >
>> > > > > git clone https://github.com/apache/drill.git
>> > > > > cd drill
>> > > > > mvn clean install
>> > > > >
>> > > > > What happens is that some modules are built successfully but
>then
>> > some
>> > > > > intermediate test fails.
>> > > > >
>> > > > > I did manage to build with
>> > > > >
>> > > > > mvn clean install -DskipTests=true
>> > > > >
>> > > > > After that,
>> > > > >
>> > > > > mvn clean install
>> > > > >
>> > > > > works as well. This suggests to me that some dependencies
>between
>> > > builds
>> > > > > and tests are not configured correctly...
>> > > > >
>> > > > > Is this known or intended?
>> > > > >
>> > > > > This happens in the master and 1.0.0 branches in the same
>way.
>> > > > >
>> > > > >
>> > > > > (2)
>> > > > >
>> > > > > Is it possible to build drill from within IntelliJIDEA?
>> > > > >
>> > > > > When I checkout the project from github and simply say
>"Build" it
>> > does
>> > > > > not know how to use antlr3 to rebuild the automatically
>generated
>> > > parser
>> > > > > code, even though I have installed the ANTLRWorks plugin and
>the
>> > maven3
>> > > > > plugin for antlr3.
>> > > > >
>> > > > > Again, this does not depend on whether I am using master or
>1.0.0.
>> > > > >
>> > > > >
>> > > > > Best regards,
>> > > > > Max.
>> > > > >
>> > > >
>> > >
>> >
>>
Re: Building question
Posted by Hanifi Gunes <hg...@maprtech.com>.
A quick advise is to reduce fork count to 1 via -DforkCount=1 -- the
default is 2.
It would be great to know which test fails or hangs though.
-Hanifi
On Wed, May 27, 2015 at 2:35 PM, George Spofford <ge...@gmail.com>
wrote:
> For what it's worth, I found that trying to build the 1.0.0 on a windows 7
> laptop with Java 7.0.55 resulted in hanging test failures as well. Wasn't
> sure if I should bother reporting but it sounds like I may be experiencing
> the same as Max.
>
> On Wed, May 27, 2015 at 2:32 PM, Hanifi Gunes <hg...@maprtech.com> wrote:
>
> > IDEA ships with built-in maven support. Only thing remains is to import
> > Drill as maven project.
> >
> > On Wed, May 27, 2015 at 2:21 PM, Chris Westin <ch...@gmail.com>
> > wrote:
> >
> > > Follow-on for (2)...
> > >
> > > At least in Eclipse, this also requires installing the maven plugin,
> and
> > > importing one or more maven project descriptions/pom.xml files
> (depending
> > > on what you're going to work on). I'd be surprised if IntelliJ doesn't
> > have
> > > something similar.
> > >
> > >
> > > On Wed, May 27, 2015 at 12:54 PM, Hanifi Gunes <hg...@maprtech.com>
> > > wrote:
> > >
> > > > 1)
> > > > - Is this known or intended?
> > > > No. Tests should run cleanly. Can you take a look at logs and post
> the
> > > > failed test along with your environment?
> > > >
> > > > 2)
> > > > - Is it possible to build drill from within IntelliJIDEA?
> > > > You should use terminal for the first time. Then IDEA picks up and
> > > cleanly
> > > > builds incremental changes.
> > > >
> > > > -Hanifi
> > > >
> > > > On Wed, May 27, 2015 at 11:13 AM, Max Neunhöffer <ma...@arangodb.com>
> > > wrote:
> > > >
> > > > > Dear Drillers,
> > > > >
> > > > > I have two questions:
> > > > >
> > > > > (1)
> > > > >
> > > > > I am trying to compile drill from source. I observe that the
> building
> > > > > instructions from the README do not work for me:
> > > > >
> > > > > git clone https://github.com/apache/drill.git
> > > > > cd drill
> > > > > mvn clean install
> > > > >
> > > > > What happens is that some modules are built successfully but then
> > some
> > > > > intermediate test fails.
> > > > >
> > > > > I did manage to build with
> > > > >
> > > > > mvn clean install -DskipTests=true
> > > > >
> > > > > After that,
> > > > >
> > > > > mvn clean install
> > > > >
> > > > > works as well. This suggests to me that some dependencies between
> > > builds
> > > > > and tests are not configured correctly...
> > > > >
> > > > > Is this known or intended?
> > > > >
> > > > > This happens in the master and 1.0.0 branches in the same way.
> > > > >
> > > > >
> > > > > (2)
> > > > >
> > > > > Is it possible to build drill from within IntelliJIDEA?
> > > > >
> > > > > When I checkout the project from github and simply say "Build" it
> > does
> > > > > not know how to use antlr3 to rebuild the automatically generated
> > > parser
> > > > > code, even though I have installed the ANTLRWorks plugin and the
> > maven3
> > > > > plugin for antlr3.
> > > > >
> > > > > Again, this does not depend on whether I am using master or 1.0.0.
> > > > >
> > > > >
> > > > > Best regards,
> > > > > Max.
> > > > >
> > > >
> > >
> >
>
Re: Building question
Posted by George Spofford <ge...@gmail.com>.
For what it's worth, I found that trying to build the 1.0.0 on a windows 7
laptop with Java 7.0.55 resulted in hanging test failures as well. Wasn't
sure if I should bother reporting but it sounds like I may be experiencing
the same as Max.
On Wed, May 27, 2015 at 2:32 PM, Hanifi Gunes <hg...@maprtech.com> wrote:
> IDEA ships with built-in maven support. Only thing remains is to import
> Drill as maven project.
>
> On Wed, May 27, 2015 at 2:21 PM, Chris Westin <ch...@gmail.com>
> wrote:
>
> > Follow-on for (2)...
> >
> > At least in Eclipse, this also requires installing the maven plugin, and
> > importing one or more maven project descriptions/pom.xml files (depending
> > on what you're going to work on). I'd be surprised if IntelliJ doesn't
> have
> > something similar.
> >
> >
> > On Wed, May 27, 2015 at 12:54 PM, Hanifi Gunes <hg...@maprtech.com>
> > wrote:
> >
> > > 1)
> > > - Is this known or intended?
> > > No. Tests should run cleanly. Can you take a look at logs and post the
> > > failed test along with your environment?
> > >
> > > 2)
> > > - Is it possible to build drill from within IntelliJIDEA?
> > > You should use terminal for the first time. Then IDEA picks up and
> > cleanly
> > > builds incremental changes.
> > >
> > > -Hanifi
> > >
> > > On Wed, May 27, 2015 at 11:13 AM, Max Neunhöffer <ma...@arangodb.com>
> > wrote:
> > >
> > > > Dear Drillers,
> > > >
> > > > I have two questions:
> > > >
> > > > (1)
> > > >
> > > > I am trying to compile drill from source. I observe that the building
> > > > instructions from the README do not work for me:
> > > >
> > > > git clone https://github.com/apache/drill.git
> > > > cd drill
> > > > mvn clean install
> > > >
> > > > What happens is that some modules are built successfully but then
> some
> > > > intermediate test fails.
> > > >
> > > > I did manage to build with
> > > >
> > > > mvn clean install -DskipTests=true
> > > >
> > > > After that,
> > > >
> > > > mvn clean install
> > > >
> > > > works as well. This suggests to me that some dependencies between
> > builds
> > > > and tests are not configured correctly...
> > > >
> > > > Is this known or intended?
> > > >
> > > > This happens in the master and 1.0.0 branches in the same way.
> > > >
> > > >
> > > > (2)
> > > >
> > > > Is it possible to build drill from within IntelliJIDEA?
> > > >
> > > > When I checkout the project from github and simply say "Build" it
> does
> > > > not know how to use antlr3 to rebuild the automatically generated
> > parser
> > > > code, even though I have installed the ANTLRWorks plugin and the
> maven3
> > > > plugin for antlr3.
> > > >
> > > > Again, this does not depend on whether I am using master or 1.0.0.
> > > >
> > > >
> > > > Best regards,
> > > > Max.
> > > >
> > >
> >
>
Re: Building question
Posted by Hanifi Gunes <hg...@maprtech.com>.
IDEA ships with built-in maven support. Only thing remains is to import
Drill as maven project.
On Wed, May 27, 2015 at 2:21 PM, Chris Westin <ch...@gmail.com>
wrote:
> Follow-on for (2)...
>
> At least in Eclipse, this also requires installing the maven plugin, and
> importing one or more maven project descriptions/pom.xml files (depending
> on what you're going to work on). I'd be surprised if IntelliJ doesn't have
> something similar.
>
>
> On Wed, May 27, 2015 at 12:54 PM, Hanifi Gunes <hg...@maprtech.com>
> wrote:
>
> > 1)
> > - Is this known or intended?
> > No. Tests should run cleanly. Can you take a look at logs and post the
> > failed test along with your environment?
> >
> > 2)
> > - Is it possible to build drill from within IntelliJIDEA?
> > You should use terminal for the first time. Then IDEA picks up and
> cleanly
> > builds incremental changes.
> >
> > -Hanifi
> >
> > On Wed, May 27, 2015 at 11:13 AM, Max Neunhöffer <ma...@arangodb.com>
> wrote:
> >
> > > Dear Drillers,
> > >
> > > I have two questions:
> > >
> > > (1)
> > >
> > > I am trying to compile drill from source. I observe that the building
> > > instructions from the README do not work for me:
> > >
> > > git clone https://github.com/apache/drill.git
> > > cd drill
> > > mvn clean install
> > >
> > > What happens is that some modules are built successfully but then some
> > > intermediate test fails.
> > >
> > > I did manage to build with
> > >
> > > mvn clean install -DskipTests=true
> > >
> > > After that,
> > >
> > > mvn clean install
> > >
> > > works as well. This suggests to me that some dependencies between
> builds
> > > and tests are not configured correctly...
> > >
> > > Is this known or intended?
> > >
> > > This happens in the master and 1.0.0 branches in the same way.
> > >
> > >
> > > (2)
> > >
> > > Is it possible to build drill from within IntelliJIDEA?
> > >
> > > When I checkout the project from github and simply say "Build" it does
> > > not know how to use antlr3 to rebuild the automatically generated
> parser
> > > code, even though I have installed the ANTLRWorks plugin and the maven3
> > > plugin for antlr3.
> > >
> > > Again, this does not depend on whether I am using master or 1.0.0.
> > >
> > >
> > > Best regards,
> > > Max.
> > >
> >
>
Re: Building question
Posted by Chris Westin <ch...@gmail.com>.
Follow-on for (2)...
At least in Eclipse, this also requires installing the maven plugin, and
importing one or more maven project descriptions/pom.xml files (depending
on what you're going to work on). I'd be surprised if IntelliJ doesn't have
something similar.
On Wed, May 27, 2015 at 12:54 PM, Hanifi Gunes <hg...@maprtech.com> wrote:
> 1)
> - Is this known or intended?
> No. Tests should run cleanly. Can you take a look at logs and post the
> failed test along with your environment?
>
> 2)
> - Is it possible to build drill from within IntelliJIDEA?
> You should use terminal for the first time. Then IDEA picks up and cleanly
> builds incremental changes.
>
> -Hanifi
>
> On Wed, May 27, 2015 at 11:13 AM, Max Neunhöffer <ma...@arangodb.com> wrote:
>
> > Dear Drillers,
> >
> > I have two questions:
> >
> > (1)
> >
> > I am trying to compile drill from source. I observe that the building
> > instructions from the README do not work for me:
> >
> > git clone https://github.com/apache/drill.git
> > cd drill
> > mvn clean install
> >
> > What happens is that some modules are built successfully but then some
> > intermediate test fails.
> >
> > I did manage to build with
> >
> > mvn clean install -DskipTests=true
> >
> > After that,
> >
> > mvn clean install
> >
> > works as well. This suggests to me that some dependencies between builds
> > and tests are not configured correctly...
> >
> > Is this known or intended?
> >
> > This happens in the master and 1.0.0 branches in the same way.
> >
> >
> > (2)
> >
> > Is it possible to build drill from within IntelliJIDEA?
> >
> > When I checkout the project from github and simply say "Build" it does
> > not know how to use antlr3 to rebuild the automatically generated parser
> > code, even though I have installed the ANTLRWorks plugin and the maven3
> > plugin for antlr3.
> >
> > Again, this does not depend on whether I am using master or 1.0.0.
> >
> >
> > Best regards,
> > Max.
> >
>
Re: Building question
Posted by Hanifi Gunes <hg...@maprtech.com>.
1)
- Is this known or intended?
No. Tests should run cleanly. Can you take a look at logs and post the
failed test along with your environment?
2)
- Is it possible to build drill from within IntelliJIDEA?
You should use terminal for the first time. Then IDEA picks up and cleanly
builds incremental changes.
-Hanifi
On Wed, May 27, 2015 at 11:13 AM, Max Neunhöffer <ma...@arangodb.com> wrote:
> Dear Drillers,
>
> I have two questions:
>
> (1)
>
> I am trying to compile drill from source. I observe that the building
> instructions from the README do not work for me:
>
> git clone https://github.com/apache/drill.git
> cd drill
> mvn clean install
>
> What happens is that some modules are built successfully but then some
> intermediate test fails.
>
> I did manage to build with
>
> mvn clean install -DskipTests=true
>
> After that,
>
> mvn clean install
>
> works as well. This suggests to me that some dependencies between builds
> and tests are not configured correctly...
>
> Is this known or intended?
>
> This happens in the master and 1.0.0 branches in the same way.
>
>
> (2)
>
> Is it possible to build drill from within IntelliJIDEA?
>
> When I checkout the project from github and simply say "Build" it does
> not know how to use antlr3 to rebuild the automatically generated parser
> code, even though I have installed the ANTLRWorks plugin and the maven3
> plugin for antlr3.
>
> Again, this does not depend on whether I am using master or 1.0.0.
>
>
> Best regards,
> Max.
>