Not exactly able to reproduce the same error currently but I see that it was related to the Drill-1024 commit where the hive-storage code was moved out of java-exec. The *drillOI* definition has moved from config.fmpp (java-exec) to config.fmpp (hive-exec).
Jenkins build was still failing in java-exec - that means that the old ObjectInspectorHelper class was still present and it was probably looking for the tdd definition in config.fmpp(java-exec).
Jenkins used 'mvn install' rather than 'mvn clean install' - maybe it was still referring to old ObjectInspectorHelper class.
Still not sure. Will try reproducing exact error.
On Tue, Jun 24, 2014 at 10:46 PM, Jacques Nadeau <[EMAIL PROTECTED]> wrote:
The final build #57 with skipping tests was successful.
Majority of the tests #55 and #56 have failed due to TimedOut exception. Other exceptions being - IllegalState(Child level allocators not closed). One instance of InterruptedException which probably occurred because of the test case termination only. On Wed, Jun 25, 2014 at 2:59 AM, Timothy Chen <[EMAIL PROTECTED]> wrote:
Yeah, we have to disable test on the apache hardware as our tests our too hungry. I'm try to get some alternatives to work. If someone wanted to try to figure out if we could run on Travis with fork 1, that would be great. Right now its failing because of the got plugin. You can try Travis on your local fork to try to find a config that works On Jun 24, 2014 8:04 PM, "Yash Sharma" <[EMAIL PROTECTED]> wrote:
The build still failed on Travis after increasing timeout to 200000ms. Need to find appropriate value for it. It fails with this error - which typically comes in timeout case: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project drill-java-exec: ExecutionException: java.lang.RuntimeException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called? [ERROR] Command was /bin/sh -c cd /home/travis/build/yssharma/incubator-drill/exec/java-exec && /usr/lib/jvm/java-7-oracle/jre/bin/java -Xms512m -Xmx2g -Ddrill.exec.http.enabled=false -Ddrill.exec.sys.store.provider.local.write=false -XX:MaxPermSize=256M -XX:MaxDirectMemorySize=2096M -XX:+CMSClassUnloadingEnabled -jar /home/travis/build/yssharma/incubator-drill/exec/java-exec/target/surefire/surefirebooter5087846151760741500.jar Will keep digging. @Jacques: I will re-submit the command line configurable patch soon. Will also dig into the surefire forks you mentioned.
Yash On Fri, Jun 27, 2014 at 12:39 AM, Yash Sharma <[EMAIL PROTECTED]> wrote:
Travis currently allows 3 gigs for entire build. If we are exceeding this then we probably should also see how we can reduce the memory footprint. Building the code in Jenkins/Travis skipping the testcases is also not very convincing.
I am on a chat with Travis guys on a different window.. Is there anything you would like me to discuss in specific?
Yash On Fri, Jun 27, 2014 at 11:27 PM, Jacques Nadeau <[EMAIL PROTECTED]> wrote:
As per discussions - 3 Gigs and 50 mins timeout is the upper limit for us from Travis's side. I have tried to run the different Test cases grouped in parallel (such that each thread gets its own 50 mins time) but that did not help us. We will have to fit in these boundaries if we are planning to go ahead with Travis.
Yash On Fri, Jun 27, 2014 at 11:55 PM, Yash Sharma <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
All projects made searchable here are trademarks of the Apache Software Foundation.
Service operated by Sematext