Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1548
Seems the reason of CI failure is irrelevant with this change. Several
tests are failed because of Livy.
```
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Zeppelin ........................................... SUCCESS [
6.867 s]
[INFO] Zeppelin: Interpreter .............................. SUCCESS [02:03
min]
[INFO] Zeppelin: Zengine .................................. SUCCESS [01:05
min]
[INFO] Zeppelin: Display system apis ...................... SUCCESS [
3.410 s]
[INFO] Zeppelin: Spark dependencies ....................... SUCCESS [
55.243 s]
[INFO] Zeppelin: Spark .................................... SUCCESS [01:53
min]
[INFO] Zeppelin: Markdown interpreter ..................... SUCCESS [
1.399 s]
[INFO] Zeppelin: Angular interpreter ...................... SUCCESS [
0.311 s]
[INFO] Zeppelin: Shell interpreter ........................ SUCCESS [
0.632 s]
[INFO] Zeppelin: Livy interpreter ......................... FAILURE [02:13
min]
[INFO] Zeppelin: HBase interpreter ........................ SKIPPED
[INFO] Zeppelin: Apache Pig Interpreter ................... SKIPPED
[INFO] Zeppelin: PostgreSQL interpreter ................... SKIPPED
[INFO] Zeppelin: JDBC interpreter ......................... SKIPPED
[INFO] Zeppelin: File System Interpreters ................. SKIPPED
[INFO] Zeppelin: Flink .................................... SKIPPED
[INFO] Zeppelin: Apache Ignite interpreter ................ SKIPPED
[INFO] Zeppelin: Kylin interpreter ........................ SKIPPED
[INFO] Zeppelin: Python interpreter ....................... SKIPPED
[INFO] Zeppelin: Lens interpreter ......................... SKIPPED
[INFO] Zeppelin: Apache Cassandra interpreter ............. SKIPPED
[INFO] Zeppelin: Elasticsearch interpreter ................ SKIPPED
[INFO] Zeppelin: BigQuery interpreter ..................... SKIPPED
[INFO] Zeppelin: Alluxio interpreter ...................... SKIPPED
[INFO] Zeppelin: web Application .......................... SKIPPED
[INFO] Zeppelin: Server ................................... SKIPPED
[INFO] Zeppelin: Packaging distribution ................... SKIPPED
[INFO] Zeppelin: Scalding interpreter ..................... SKIPPED
[INFO] Zeppelin: Examples ................................. SKIPPED
[INFO] Zeppelin: Example application - Clock .............. SKIPPED
[INFO] Zeppelin: Example application - Horizontal Bar chart SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 08:24 min
[INFO] Finished at: 2016-11-01T18:59:03+00:00
[INFO] Final Memory: 62M/407M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) on
project zeppelin-livy: Error resolving project artifact: Could not transfer
artifact org.mortbay.jetty:jetty:pom:6.1.26.cloudera.4 from/to sonatype-apache
(https://repository.apache.org/releases/): Connect to repository.apache.org:443
[repository.apache.org/207.244.88.143] failed: Connection timed out for project
org.mortbay.jetty:jetty:jar:6.1.26.cloudera.4 ->
```
@meenakshisekar The latest change is looks good to me. Just in case, could
you retrigger CI again? At least Livy won't be the failure reason.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
