Conversation
|
I've completed my review. The changes are well-structured across three logical commits and look correct. Let me verify there are no issues:
LGTM |
|
The generated output of |
baafc59 to
5432e59
Compare
Merging this PR will not alter performance
Comparing Footnotes
|
Update protobuf, which allows us to use prebuilt protoc (in the common case, exceptions for perfetto may apply), and drop a bunch of the remaining autoloads (after adding some repo overrides at least). Also add missing loads for sqlite3.
Enable incompatible_repo_env_ignores_action_env, which is already the default in Bazel 9. BAZEL_COMPILER, CC, BAZEL_USE_LLVM_NATIVE_COVERAGE, GCOV, AR, and BAZEL_LLVM_COV variables are only provided as repo_env now. ASAN_OPTIONS and UBSAN_OPTIONS are only provided as action_env. COVERAGE_GCOV_PATH might be needed for both and continues to be provided as both repo and action env.
5432e59 to
2b78130
Compare
[build] Fix and enable bazel incompatible_use_default_test_toolchainThis will be required with Bazel 10
=> This proved to be too difficult to figure out now, I was able to fix the build with the flag enabled but it looks like bazel might end up building host tools for the target platform?
[build] Update protobuf to v34, restrict autoloads further
Update protobuf, which allows us to use prebuilt protoc (in the common case, exceptions for perfetto may apply), and drop a bunch of the remaining autoloads (after adding an override for rules_go at least). Also add missing loads for sqlite3.
[build] Flip --incompatible_repo_env_ignores_action_env
Enable incompatible_repo_env_ignores_action_env, which is already the default in Bazel 9. BAZEL_COMPILER, CC, BAZEL_USE_LLVM_NATIVE_COVERAGE, GCOV, AR, and BAZEL_LLVM_COV variables are only provided as repo_env now. ASAN_OPTIONS and UBSAN_OPTIONS are only provided as action_env. COVERAGE_GCOV_PATH might be needed for both and continues to be provided as both repo and action env.