Bazel CI config: remove --incompatible_use_python_toolchains=false #1224
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Profpatsch
approved these changes
Jan 29, 2020
mboes
force-pushed
the
bazel-ci-python-toolchain
branch
from
ab491c0 to
9d44c7f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We removed that flag on our own CI configuration in #1142 but left the Bazel CI untouched. The flag seems to be causing #1217. At least I was able to reproduce the same error on our CI by upgrading to Bazel 2.0.0 and setting
--incompatible_use_python_toolchains=false, see https://buildkite.com/tweag-1/rules-haskell/builds/956#5d3f6ff7-596b-4720-bceb-87d79ae80839/21-2292.Closes #1217