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

workspace: upgrade to Bazel 3.0.0, rules_rust latest #4296

Closed
wants to merge 1 commit into from

Conversation

wchargin
Copy link
Contributor

@wchargin wchargin commented Nov 9, 2020

Summary:
Bazel rule repositories (Go, Rust, protobuf, …) are migrating to a new
linker API introduced as a breaking Bazel change:
bazelbuild/bazel#10860

This API requires Bazel 3.0.0, which is fine for us.

Test Plan:
Everything builds, all tests pass, and TensorBoard looks okay enough,
including the dynamically loaded projector plugin.

wchargin-branch: bazel-3.0.0

Summary:
Bazel rule repositories (Go, Rust, protobuf, …) are migrating to a new
linker API introduced as a breaking Bazel change:
<bazelbuild/bazel#10860>

This API requires Bazel 3.0.0, which is fine for us.

Test Plan:
Everything builds, all tests pass, and TensorBoard looks okay enough.

wchargin-branch: bazel-3.0.0
wchargin-source: 5c02209b5c25cbeab580c28c549df53c6d501ae4
@wchargin
Copy link
Contributor Author

wchargin commented Nov 9, 2020

Sent upstream bazelbuild/rules_rust#484 for CI
error, but @stephanwlee tells me that we need Bazel 3.5.0 anyway, so we
might as well just do that instead rather than as a follow-up. Easier on
CI caches this way, too. Will supersede with #4301.

@wchargin wchargin closed this Nov 9, 2020
@wchargin wchargin deleted the wchargin-bazel-3.0.0 branch December 15, 2020 07:15
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.

None yet

1 participant