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 2017/02/17 12:39:10 UTC
[GitHub] zeppelin pull request #2033: [ZEPPELIN-2129] [HOTFIX] Flaky test - PySparkIn...
GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/zeppelin/pull/2033
[ZEPPELIN-2129] [HOTFIX] Flaky test - PySparkInterpreterTest
### What is this PR for?
testing/install_external_dependencies.sh installs latest version of miniconda for python/pyspark testing.
It looks like miniconda just released new version and latest version of miniconda3 looks like using python 3.6.
And pyspark has problem with python 3.6 https://issues.apache.org/jira/browse/SPARK-19019.
This PR fix the miniconda version to previous one.
### What type of PR is it?
Hot Fix
### Todos
* [x] - force fix miniconda version
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-2129
### How should this be tested?
CI gree
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Leemoonsoo/zeppelin ZEPPELIN-2129
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2033.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 #2033
----
commit 5b343d55ca6e37d1b1a2467c928638e0ec1c5ba2
Author: Lee moon soo <mo...@apache.org>
Date: 2017-02-17T12:30:58Z
force set miniconda version
----
---
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 #2033: [ZEPPELIN-2129] [HOTFIX] Flaky test - PySparkIn...
Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo closed the pull request at:
https://github.com/apache/zeppelin/pull/2033
---
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 #2033: [ZEPPELIN-2129] [HOTFIX] Flaky test - PySparkIn...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2033
---
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 #2033: [ZEPPELIN-2129] [HOTFIX] Flaky test - PySparkIn...
Posted by Leemoonsoo <gi...@git.apache.org>.
GitHub user Leemoonsoo reopened a pull request:
https://github.com/apache/zeppelin/pull/2033
[ZEPPELIN-2129] [HOTFIX] Flaky test - PySparkInterpreterTest
### What is this PR for?
testing/install_external_dependencies.sh installs latest version of miniconda for python/pyspark testing.
It looks like miniconda just released new version and latest version of miniconda3 looks like using python 3.6.
And pyspark has problem with python 3.6 https://issues.apache.org/jira/browse/SPARK-19019.
This PR fix the miniconda version to previous one.
### What type of PR is it?
Hot Fix
### Todos
* [x] - force fix miniconda version
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-2129
### How should this be tested?
CI gree
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Leemoonsoo/zeppelin ZEPPELIN-2129
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2033.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 #2033
----
commit 5b343d55ca6e37d1b1a2467c928638e0ec1c5ba2
Author: Lee moon soo <mo...@apache.org>
Date: 2017-02-17T12:30:58Z
force set miniconda version
----
---
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 #2033: [ZEPPELIN-2129] [HOTFIX] Flaky test - PySparkInterpret...
Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2033
CI became green.
While CI test on all PRs are failing because of this problem, I'm merging it to master as a hot fix.
---
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.
---