[GitHub] zeppelin issue #928: [ZEPPELIN-116] Add Mahout Support for Spark Interpreter
Github user rawkintrevo commented on the issue: https://github.com/apache/zeppelin/pull/928 last commit was to get around that web application fail. Added my own logging to shed some light on the situation: `21:59:21,200 INFO org.apache.zeppelin.rest.AbstractTestRestApi:134 - pySparkTest: %text pyspark is not responding` --- 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. ---
[GitHub] zeppelin issue #928: [ZEPPELIN-116] Add Mahout Support for Spark Interpreter
Github user bzz commented on the issue: https://github.com/apache/zeppelin/pull/928 Looks at latest CI results, I do not think that comment above is relevant any more, esp for the first and most general CI profile. Great progress @rawkintrevo ! --- 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. ---
[GitHub] zeppelin issue #928: [ZEPPELIN-116] Add Mahout Support for Spark Interpreter
Github user bzz commented on the issue: https://github.com/apache/zeppelin/pull/928 ### CI failure debug approach First thing to do in order to debug such issues: - link all raw build logs - extact and systematize failure resaons from logs (usulaly it's last 'exited with 1' message + first exception) - cross-check them with list of [flaky-tests in JIRA](https://issues.apache.org/jira/browse/ZEPPELIN-862?jql=project%20%3D%20ZEPPELIN%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20labels%20%3D%20flaky-test) Usually, after all this is done and posted - it is much easier for other people to jump in and help in the drive-by reviews. ### CI failures in this PR 1. `ZeppelinSparkClusterTest` in Zeppelin Server failing Profiles # [1](https://api.travis-ci.org/jobs/141222530/log.txt?deansi=true), [2](https://api.travis-ci.org/jobs/141222531/log.txt?deansi=true), [3](https://api.travis-ci.org/jobs/141222532/log.txt?deansi=true), ``` Failed tests: ZeppelinSparkClusterTest.pySparkDepLoaderTest:231 expected: but was: ZeppelinSparkClusterTest.pySparkAutoConvertOptionTest:152 expected: but was: ZeppelinSparkClusterTest.pySparkTest:127 expected: but was: Tests run: 63, Failures: 3, Errors: 0, Skipped: 0 ``` Profile [4](https://api.travis-ci.org/jobs/141222533/log.txt?deansi=true) has only single test failure ``` Results : Failed tests: ZeppelinSparkClusterTest.pySparkTest:127 expected: but was: Tests run: 40, Failures: 1, Errors: 0, Skipped: 0 ``` Profile [6](https://api.travis-ci.org/jobs/141222535/log.txt?deansi=true) have even more tests ``` Running org.apache.zeppelin.rest.ZeppelinSparkClusterTest 5:06:37,836 INFO org.apache.zeppelin.notebook.Paragraph:252 - run paragraph 20160630-050637_1289828172 using spark org.apache.zeppelin.interpreter.LazyOpenInterpreter@62b97ff1 Exception in thread "pool-1-thread-3" java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.softValues()Lcom/google/common/collect/MapMaker; from class org.apache.spark.SparkEnv at org.apache.spark.SparkEnv.(SparkEnv.scala:75) at org.apache.spark.SparkEnv$.create(SparkEnv.scala:272) at org.apache.spark.SparkContext.(SparkContext.scala:204) at org.apache.zeppelin.spark.SparkInterpreter.createSparkContext(SparkInterpreter.java:338) at org.apache.zeppelin.spark.SparkInterpreter.getSparkContext(SparkInterpreter.java:122) at org.apache.zeppelin.spark.SparkInterpreter.open(SparkInterpreter.java:513) at org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:69) at org.apache.zeppelin.interpreter.LazyOpenInterpreter.getProgress(LazyOpenInterpreter.java:110) at org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer.getProgress(RemoteInterpreterServer.java:404) at org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Processor$getProgress.getResult(RemoteInterpreterService.java:1509) at org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Processor$getProgress.getResult(RemoteInterpreterService.java:1494) at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39) at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39) at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:285) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) . Failed tests: ZeppelinSparkClusterTest.pySparkDepLoaderTest:195->getSparkVersionNumber:250 expected: but was: ZeppelinSparkClusterTest.pySparkAutoConvertOptionTest:139->getSparkVersionNumber:250 expected: but was: ZeppelinSparkClusterTest.basicRDDTransformationAndActionTest:81 expected: but was: ZeppelinSparkClusterTest.pySparkTest:115->getSparkVersionNumber:250 expected: but was: ZeppelinSparkClusterTest.zRunTest:180 expected: but was: ZeppelinSparkClusterTest.sparkRTest:90->getSparkVersionNumber:250 expected: but was: ``` 1. `ZeppelinSparkClusterTest` hangs AKA [ZEPPELIN-862](https://issues.apache.org/jira/browse/ZEPPELIN-862) Profile [5](https://api.travis-ci.org/jobs/141222534/log.txt?deansi=true) ``` Running org.apache.zeppelin.rest.ZeppelinSparkClusterTest ... No output has been received in the last 10 minutes, this potentially indicates a stalled build or something wrong with the build itself. The build has been terminated ``` This guys is known and flaky, so it's better to focus on the rest issues for now.
[GitHub] zeppelin issue #928: [ZEPPELIN-116] Add Mahout Support for Spark Interpreter
Github user rawkintrevo commented on the issue: https://github.com/apache/zeppelin/pull/928 @bzz I've rebased to master twice now. The failures are on: - Zeppelin Server: Connection Refused - Mahout : Out of Memory `mvn clean verify` works for me locally under a variety of circumstances. I don't know much about trouble shooting travis builds. I know you have 0.6 rolling out and are busy, but please take a quick look and / or point me to resources/give me some hints for solving these issues. Thanks! tg --- 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. ---
[GitHub] zeppelin issue #928: [ZEPPELIN-116] Add Mahout Support for Spark Interpreter
Github user rawkintrevo commented on the issue: https://github.com/apache/zeppelin/pull/928 Also OOM errors in the actual Mahout interpretter... --- 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. ---
[GitHub] zeppelin issue #928: [ZEPPELIN-116] Add Mahout Support for Spark Interpreter
Github user rawkintrevo commented on the issue: https://github.com/apache/zeppelin/pull/928 Also OOM errors in the actual Mahout interpretter... --- 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. ---
[GitHub] zeppelin issue #928: [ZEPPELIN-116] Add Mahout Support for Spark Interpreter
Github user rawkintrevo commented on the issue: https://github.com/apache/zeppelin/pull/928 Merged Master- still failing on Zeppelin Server at ``` 15:27:30,479 ERROR org.apache.zeppelin.rest.AbstractTestRestApi:251 - Exception in AbstractTestRestApi while checkIfServerIsRunning java.net.ConnectException: Connection refused ``` --- 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. ---
[GitHub] zeppelin issue #928: [ZEPPELIN-116] Add Mahout Support for Spark Interpreter
Github user rawkintrevo commented on the issue: https://github.com/apache/zeppelin/pull/928 @bzz I can imagine. Builds are still failling at random,and I'm not sure what to make of it. mvn clean verify works well on my system. Let me know if there is anymore I can do to test/work on this for you. tg --- 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. ---
[GitHub] zeppelin issue #928: [ZEPPELIN-116] Add Mahout Support for Spark Interpreter
Github user bzz commented on the issue: https://github.com/apache/zeppelin/pull/928 That sounds great @rawkintrevo on licenses ! Sorry, in preparation to 0.6 release people get quite busy.. --- 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. ---
[GitHub] zeppelin issue #928: [ZEPPELIN-116] Add Mahout Support for Spark Interpreter
Github user rawkintrevo commented on the issue: https://github.com/apache/zeppelin/pull/928 Lot's of connection test failures when building Zeppelin-Server? --- 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. ---
