[
https://issues.apache.org/jira/browse/FLINK-19389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17201935#comment-17201935
]
Di Xu commented on FLINK-19389:
-------------------------------
Not really, I think it affects both non-linux and linux environments b/c in any
case we needs to start the fileserver during docker build, am I right?
But when there is only python2 installed on the test env, it will not trigger
the problem ... So I guess it is the case in the CI vm..
> Error determining python major version to start fileserver during e-2-e tests
> -----------------------------------------------------------------------------
>
> Key: FLINK-19389
> URL: https://issues.apache.org/jira/browse/FLINK-19389
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Reporter: Di Xu
> Priority: Major
>
> Currently the logic to determine python version in command-docker.sh[1] has
> an error:
> * when there is only python3 installed, `command -v python` also returns 0
> and then `python (actually 3) python2_fileserver.py` will be executed then
> it causes an error
> * in the case of python version management tool pyenv[2] is used, the soft
> link to python3 would exist even if user switched to python2, so simply check
> python3 before python(2) will NOT solve the problem.
> The suggested way is:
> python -c 'import sys; print(sys.version_info.major)'
>
> [1]
> [https://github.com/apache/flink/blob/master/flink-end-to-end-tests/test-scripts/common_docker.sh#L57]
> [2] [https://github.com/pyenv/pyenv]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
