Skip to content

Conversation

@wchargin
Copy link
Contributor

@wchargin wchargin commented Aug 9, 2019

Summary:
This expands our forward-compatibility window to at least 0.29.0rc4 by
opting out of the --incompatible_use_python_toolchains flag whose
default was flipped in 0.27.0 (see #2355).

Fixes #2534.

Test Plan:
On Bazel 0.29.0rc4, verify that //tensorboard fetches, builds, and
runs correctly and that all tests pass, without the need to manually
specify any flags to Bazel.

wchargin-branch: bazelrc-toolchains

Summary:
This expands our forward-compatibility window to at least 0.29.0rc4 by
opting out of the `--incompatible_use_python_toolchains` flag whose
default was flipped in 0.27.0 (see #2355).

Test Plan:
On Bazel 0.29.0rc4, verify that `//tensorboard` builds and runs
correctly and that all tests pass, without the need to manually specify
any flags to Bazel.

wchargin-branch: bazelrc-toolchains
.bazelrc Outdated
@@ -0,0 +1 @@
common --incompatible_use_python_toolchains=false
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe let's add a comment referencing the issue that requires this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

wchargin-source: 1c1d54469ce7d63c1b8415eb3d1511958ed63aa5
wchargin-branch: bazelrc-toolchains
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Build does not use proper Python path (Following instructions in DEVELOPMENT.md)

4 participants