Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1248
Thanks! In my experience, if in case of CI failure PR author posts the
failure result from logs - that speeds us review a lot!
CI fails now on Spark 1.6 Scala 2.10 and Scala 2.11 profiles with
```
[INFO] Zeppelin: web Application .......................... FAILURE [01:31
min]
[INFO] make: Leaving directory
`/home/travis/build/apache/zeppelin/zeppelin-web/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/build'
[ERROR] npm ERR! Linux 3.13.0-40-generic
[ERROR] npm ERR! argv
"/home/travis/build/apache/zeppelin/zeppelin-web/node/node"
"/home/travis/build/apache/zeppelin/zeppelin-web/node/node_modules/npm/bin/npm-cli.js"
"install" "--color=false"
[ERROR] npm ERR! node v0.12.13
[ERROR] npm ERR! npm v2.15.0
[ERROR] npm ERR! code ECONNRESET
[ERROR] npm ERR! errno ECONNRESET
[ERROR] npm ERR! syscall read
[ERROR]
[ERROR] npm ERR! network read ECONNRESET
[ERROR] npm ERR! network This is most likely not a problem with npm itself
[ERROR] npm ERR! network and is related to network connectivity.
[ERROR] npm ERR! network In most cases you are behind a proxy or have bad
network settings.
[ERROR] npm ERR! network
[ERROR] npm ERR! network If you are behind a proxy, please make sure that
the
[ERROR] npm ERR! network 'proxy' config is set properly. See: 'npm help
config'
```
Which seems to be networking issue on Travis side ð
Thank you @mwkang , looks great to me, merging to master if there is no
further discussion.
---
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.
---
