Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1461
@corneadoug rebased but it still failed in Selenium test. The error log is
like below
```
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 76.542 sec
- in org.apache.zeppelin.integration.SparkParagraphIT
Results :
Failed tests:
ParagraphActionsIT.testWidth:314 New Width is : 4
Expected: <true>
but: was <false>
ParagraphActionsIT.testWidth:314 New Width is : 8
Expected: <true>
but: was <false>
Tests in error:
ZeppelinIT.testSparkInterpreterDependencyLoading:234->AbstractZeppelinIT.waitForParagraph:70->AbstractZeppelinIT.pollingWait:96
û Timeout
Tests run: 16, Failures: 2, Errors: 1, Skipped: 0
[INFO]
[INFO] --- scalatest-maven-plugin:1.0:test (test) @ zeppelin-server ---
[36mDiscovery starting.[0m
Oct 06, 2016 8:09:31 AM org.openqa.selenium.safari.SafariDriverServer start
INFO: Server started on port 13724
Oct 06, 2016 8:09:31 AM
org.openqa.selenium.safari.SafariDriverCommandExecutor stop
INFO: Shutting down
Oct 06, 2016 8:09:31 AM
org.openqa.selenium.safari.SafariDriverCommandExecutor stop
INFO: Stopping server
Oct 06, 2016 8:09:31 AM org.openqa.selenium.safari.SafariDriverServer stop
INFO: Stopping server
Oct 06, 2016 8:09:31 AM
org.openqa.selenium.safari.SafariDriverCommandExecutor stop
INFO: Shutdown complete
[36mDiscovery completed in 4 seconds, 967 milliseconds.[0m
[36mRun starting. Expected test count is: 1[0m
Zeppelin is already running
[32mWelcomePageSuite:[0m
[32m- Welcome sign is correct[0m
Zeppelin stop [60G[[1;32m OK [0;39m]
[36mRun completed in 13 seconds, 782 milliseconds.[0m
[36mTotal number of tests run: 1[0m
[36mSuites: completed 3, aborted 0[0m
[36mTests: succeeded 1, failed 0, canceled 0, ignored 0, pending 0[0m
[32mAll tests passed.[0m
[INFO]
[INFO] --- maven-antrun-plugin:1.7:run (stop-zeppelin) @ zeppelin-server ---
[INFO] Executing tasks
main:
[exec] Zeppelin is not running
[INFO] Executed tasks
[INFO]
[INFO] --- maven-failsafe-plugin:2.16:verify (default) @ zeppelin-server ---
[INFO] Failsafe report directory:
/home/travis/build/apache/zeppelin/zeppelin-server/target/failsafe-reports
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Zeppelin: Interpreter .............................. SUCCESS [
12.285 s]
[INFO] Zeppelin: Zengine .................................. SUCCESS [
6.291 s]
[INFO] Zeppelin: Display system apis ...................... SUCCESS [
3.479 s]
[INFO] Zeppelin: Spark dependencies ....................... SUCCESS [
37.316 s]
[INFO] Zeppelin: Spark .................................... SUCCESS [
6.898 s]
[INFO] Zeppelin: Server ................................... FAILURE [09:22
min]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 10:29 min
[INFO] Finished at: 2016-10-06T08:09:45+00:00
[INFO] Final Memory: 46M/376M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-failsafe-plugin:2.16:verify (default) on project
zeppelin-server: There are test failures.
[ERROR]
[ERROR] Please refer to
/home/travis/build/apache/zeppelin/zeppelin-server/target/failsafe-reports for
the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :zeppelin-server
```
Seems not irrelevant with this change :)
---
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.
---
