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.

Sign up for GitHub

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

Jump to bottom

//:remote_client does not build with bazel 6.2 #28

Closed
werkt opened this issue May 10, 2023 · 0 comments · Fixed by #30
Closed

//:remote_client does not build with bazel 6.2 #28

werkt opened this issue May 10, 2023 · 0 comments · Fixed by #30
Assignees
@werkt

Comments

@werkt
Copy link
Member

werkt commented May 10, 2023 •
edited
Loading

Failure is documented in a buildfarm build of remote_client used for its Cache Check:

https://buildkite.com/bazel/buildfarm-farmer/builds/6392#018806c4-af5b-4d0a-97fc-af377db2340b

Temporary fixes (some are to be fixed in later upstream) for the entirety of a resolution should be applied to this project.

Bazel version should be indicated with a .bazelversion to prevent bazelisk-based failures and identify support.
@werkt werkt self-assigned this May 10, 2023
werkt added a commit that referenced this issue May 10, 2023
@werkt
Update tools_remote deps for bazel 6.2
1b49ba6 
Bazel 6.2 has introduced warnings promoted to errors via jdk flags that
prevent grpc 1.44.1 from working. Upgrading that to 1.55.1

This introduced an incompatibility with rules_skylib. Upgrading that to
1.4.1 from 0.9.0.
Also incompatible was rules_jvm_external, which was upgraded to 5.2 from
4.2.
Lastly, absl as used by protobuf at the new grpc version is incompatible
with < c++14. Introduced a .bazelrc as a poor excuse for toolchain
injection. Bazel will default to c++14 (from c++0x) with a release that
includes bazelbuild/bazel#18280. An issue to
remove this file will follow.

Tagged the build with .bazelversion to avoid accidental consumption of
incompatible bazels with bazelisk.

Fixes #28
@werkt werkt mentioned this issue May 10, 2023
Merged
@werkt werkt closed this as completed in #30 May 10, 2023
werkt added a commit that referenced this issue May 10, 2023
@werkt
Update tools_remote deps for bazel 6.2 (#30)
6f311ad 
Bazel 6.2 has introduced warnings promoted to errors via jdk flags that
prevent grpc 1.44.1 from working. Upgrading that to 1.55.1

This introduced an incompatibility with rules_skylib. Upgrading that to
1.4.1 from 0.9.0.
Also incompatible was rules_jvm_external, which was upgraded to 5.2 from
4.2.
Lastly, absl as used by protobuf at the new grpc version is incompatible
with < c++14. Introduced a .bazelrc as a poor excuse for toolchain
injection. Bazel will default to c++14 (from c++0x) with a release that
includes bazelbuild/bazel#18280. An issue to
remove this file will follow.

Tagged the build with .bazelversion to avoid accidental consumption of
incompatible bazels with bazelisk.

Fixes #28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@werkt werkt

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update tools_remote deps for bazel 6.2 buildfarm/tools_remote
1 participant
@werkt