Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

//internal/common:check_version_test breaks with Bazel HEAD #832

Closed
laszlocsomor opened this issue Jun 7, 2019 · 2 comments
Closed

//internal/common:check_version_test breaks with Bazel HEAD #832

laszlocsomor opened this issue Jun 7, 2019 · 2 comments

Comments

@laszlocsomor
Copy link
Contributor

CI link: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1026#47ba3e35-d7ad-4ca8-9439-0bd8e9f602e9

Source tree: 4c62d33

Bazel version: built at bazelbuild/bazel@12c7942

Test log:

exec ${PAGER:-/usr/bin/less} "$0" || exit 1
Executing tests from //internal/common:check_version_test
-----------------------------------------------------------------------------
Error occurred while attempting to use the default Python toolchain (@bazel_tools//tools/python:autodetecting_toolchain).
According to '/usr/bin/python -V', version is 'Python 2.7.10', but we need version 3. PATH is:

.:/bin:/usr/bin

Please ensure an interpreter with version 3 is available on this platform as 'python3' or 'python', or else register an appropriate Python toolchain as per the documentation for py_runtime_pair (https://github.com/bazelbuild/bazel/blob/master/tools/python/toolchain.bzl).

Note that prior to Bazel 0.27, there was no check to ensure that the interpreter's version matched the version declared by the target (#4815). If your build worked prior to Bazel 0.27, and you're sure your targets do not require Python 3, you can opt out of this version check by using the non-strict autodetecting toolchain instead of the standard autodetecting toolchain. This can be done by passing the flag `--extra_toolchains=@bazel_tools//tools/python:autodetecting_toolchain_nonstrict` on the command line or adding it to your bazelrc.
@laurentlb
Copy link
Contributor

cc @brandjon

@brandjon
Copy link
Contributor

brandjon commented Jun 7, 2019

Dup of #809.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants