Github user echarles commented on the issue:
https://github.com/apache/zeppelin/pull/932
@bzz are we ok now with the license information?
Travis is red for 3 on the 9 profiles, but this comes from a timeout trying
to launch/access spark
```16/08/17 15:36:04 INFO ExecutorRunner: Launch command:
"/usr/lib/jvm/java-7-oracle/bin/java" "-cp"
"/home/travis/build/apache/zeppelin/spark-1.6.1-bin-hadoop2.3/conf/:/home/travis/build/apache/zeppelin/spark-1.6.1-bin-hadoop2.3/lib/spark-assembly-1.6.1-hadoop2.3.0.jar:/home/travis/build/apache/zeppelin/spark-1.6.1-bin-hadoop2.3/lib/datanucleus-core-3.2.10.jar:/home/travis/build/apache/zeppelin/spark-1.6.1-bin-hadoop2.3/lib/datanucleus-api-jdo-3.2.6.jar:/home/travis/build/apache/zeppelin/spark-1.6.1-bin-hadoop2.3/lib/datanucleus-rdbms-3.2.9.jar"
"-Xms1024M" "-Xmx1024M" "-Dspark.driver.port=47348" "-XX:MaxPermSize=256m"
"org.apache.spark.executor.CoarseGrainedExecutorBackend" "--driver-url"
"spark://[email protected]:47348" "--executor-id" "0"
"--hostname" "172.17.14.104" "--cores" "2" "--app-id" "app-20160817153604-0003"
"--worker-url" "spark://[email protected]:41888"
16/08/17 15:36:40 INFO Worker: Asked to kill executor
app-20160817153604-0003/0
16/08/17 15:36:40 INFO ExecutorRunner: Runner thread for executor
app-20160817153604-0003/0 interrupted
16/08/17 15:36:40 INFO ExecutorRunner: Killing process!
16/08/17 15:36:41 INFO Worker: Executor app-20160817153604-0003/0 finished
with state KILLED exitStatus 143
16/08/17 15:36:41 INFO Worker: Cleaning up local directories for
application app-20160817153604-0003
16/08/17 15:36:41 INFO ExternalShuffleBlockResolver: Application
app-20160817153604-0003 removed, cleanupLocalDirs = true
travis_time:end:17fafc60:start=1471448259153159015,finish=1471448259166402551,duration=13243536
```
Anything else I can do to get this merged?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
