Github user BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/17355#discussion_r107755248
--- Diff: dev/run-pip-tests ---
@@ -75,18 +81,24 @@ for python in "${PYTHON_EXECS[@]}"; do
echo "Using $VIRTUALENV_BASE for virtualenv"
VIRTUALENV_PATH="$VIRTUALENV_BASE"/$python
rm -rf "$VIRTUALENV_PATH"
- mkdir -p "$VIRTUALENV_PATH"
- virtualenv --python=$python "$VIRTUALENV_PATH"
- source "$VIRTUALENV_PATH"/bin/activate
- # Upgrade pip & friends
- pip install --upgrade pip pypandoc wheel
- pip install numpy # Needed so we can verify mllib imports
+ if [ -n "$USE_CONDA" ]; then
+ conda create -y -p "$VIRTUALENV_PATH" python=$python numpy pandas
pip setuptools
--- End diff --
Setting `python=$python` led to "python=3" which then tried to install
python 3.6
```
+ conda create -y -p /tmp/tmp.OymEZOKFzo/3 python=3 numpy pandas pip
setuptools
Fetching package metadata .........
Solving package specifications: .
Package plan for installation in environment /tmp/tmp.OymEZOKFzo/3:
The following NEW packages will be INSTALLED:
mkl: 2017.0.1-0
numpy: 1.12.1-py36_0
openssl: 1.0.2k-1
pandas: 0.19.2-np112py36_1
pip: 9.0.1-py36_1
python: 3.6.1-0
...
```
And that led to a conflict with pypandoc:
```
UnsatisfiableError: The following specifications were found to be in
conflict:
- pypandoc -> python 3.5* -> sqlite 3.9.*
- pypandoc -> python 3.5* -> xz 5.0.*
- python 3.6*
```
manually setting "python=3.5" seemed to clear things up so it could
complete the test
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
