Github user doanduyhai commented on the issue:
https://github.com/apache/zeppelin/pull/746
Ok, there are 3 unrelated errors:
1) https://s3.amazonaws.com/archive.travis-ci.org/jobs/155941982/log.txt
```
[32mAngularElem[0m
[31m- should provide onclick method *** FAILED ***[0m
[31m The code passed to eventually never returned normally. Attempted 1
times over 208.64569899999998 milliseconds. Last failure message: 0 was not
equal to 1. (AbstractAngularElemTest.scala:72)[0m
```
The test timeoud because the default implicit for Scala `eventually {a
should be(1)}` is only 150ms. Timeout is a recurrent issue when running in
containers in Travis
2) https://s3.amazonaws.com/archive.travis-ci.org/jobs/155941985/log.txt
Some flaky remote interpreter test. When running locally the test with `mvn
test
-Dtest=org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcessTest` it
is successful:
```
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcessTest
16:48:19,231 INFO
org.apache.zeppelin.interpreter.remote.RemoteInterpreterManagedProcess:116 -
Run interpreter process [../bin/interpreter.sh, -d, nonexists, -p, 64503, -l,
fakeRepo]
16:48:20,317 INFO
org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess:127 - shutdown
interpreter process
16:48:22,579 INFO
org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess:137 - Exception
in RemoteInterpreterProcess while synchronized dereference, can safely ignore
exception while client.shutdown() may terminates remote process
16:48:22,580 INFO
org.apache.zeppelin.interpreter.remote.RemoteInterpreterManagedProcess:154 -
Interpreter process exited 0
16:48:23,103 INFO
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer:89 - Starting
remote interpreter server on port 3678
16:48:23,471 INFO
org.apache.zeppelin.interpreter.remote.RemoteInterpreterManagedProcess:116 -
Run interpreter process [../bin/interpreter.sh, -d, nonexists, -p, 64509, -l,
fakeRepo]
16:48:23,979 INFO
org.apache.zeppelin.interpreter.remote.RemoteInterpreterManagedProcess:116 -
Run interpreter process [../bin/interpreter.sh, -d, nonexists, -p, 64512, -l,
fakeRepo]
16:48:24,485 INFO
org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess:127 - shutdown
interpreter process
16:48:26,630 INFO
org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess:137 - Exception
in RemoteInterpreterProcess while synchronized dereference, can safely ignore
exception while client.shutdown() may terminates remote process
16:48:26,632 INFO
org.apache.zeppelin.interpreter.remote.RemoteInterpreterManagedProcess:154 -
Interpreter process exited 0
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.076 sec -
in org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcessTest
Results :
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
```
3) https://s3.amazonaws.com/archive.travis-ci.org/jobs/155942015/log.txt
Just a classical NPM download failure:
```
[INFO] --- frontend-maven-plugin:0.0.25:npm (npm install) @ zeppelin-web ---
[INFO] Running 'npm install --color=false' in
/home/travis/build/apache/zeppelin/zeppelin-web
[ERROR] npm WARN deprecated minimatch@0.2.14: Please update to minimatch
3.0.2 or higher to avoid a RegExp DoS issue
[ERROR] npm WARN deprecated minimatch@2.0.10: Please update to minimatch
3.0.2 or higher to avoid a RegExp DoS issue
[ERROR] npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and
before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0
as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
[ERROR] npm WARN deprecated minimatch@0.3.0: Please update to minimatch
3.0.2 or higher to avoid a RegExp DoS issue
[ERROR] npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer
maintained. Upgrade to lodash@^4.0.0.
[ERROR] npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and
before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0
as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
[ERROR] npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing
Set-Cookie https://nodesecurity.io/advisories/130
[ERROR] npm WARN deprecated CSSselect@0.7.0: the module is now available as
'css-select'
[ERROR] npm WARN deprecated CSSwhat@0.4.7: the module is now available as
'css-what'
[ERROR] npm WARN optional dep failed, continuing fsevents@1.0.14
[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'
[INFO]
[INFO] > ws@0.4.32 install
/home/travis/build/apache/zeppelin/zeppelin-web/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
[INFO] > (node-gyp rebuild 2> builderror.log) || (exit 0)
```
@felixcheung @jongyoul Can we merge this and move on ? This PR has been
there for a while and I have re-based it many times against master
---
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.
---
