You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by Leemoonsoo <gi...@git.apache.org> on 2016/06/24 02:06:12 UTC
[GitHub] zeppelin pull request #1078: [TEST] Flaky test
GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/zeppelin/pull/1078
[TEST] Flaky test
Test for hanging ci build
```
Spark version detected 1.6.1
23:52:30,005 INFO org.apache.zeppelin.notebook.Paragraph:252 - run paragraph 20160623-235230_1368989448 using r org.apache.zeppelin.interpreter.LazyOpenInterpreter@5221ff81
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
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Leemoonsoo/zeppelin disable_flaky_test
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1078.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1078
----
commit bdaa411e837c746c167b6ec91d87e09ca03140f8
Author: Lee moon soo <mo...@apache.org>
Date: 2016-06-24T02:05:30Z
trigger ci
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #1078: [ZEPPELIN-936] Fix flaky test SparkRTest
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1078
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #1078: [ZEPPELIN-936] Fix flaky test SparkRTest
Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1078
I think the reason SparkRTest() failing was because of resource.
pySpark() test creates 33 python processes (num core + 1) and that seems make unable to run SparkRTest().
I have changed `spark.core.max` property to 2 for CI test, so now only 3 python processes are created. Triggered CI couple of times with these changes. I still see some CI failure by network fault or the other flaky tests, but can not see SparkRTest() failure anymore.
I'm merging it into master and branch-0.6 as a hotfix.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---