You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Incompatible flag --incompatible_config_setting_private_default_visibility will be enabled by default in the next major release (Bazel 7.0), thus breaking Cloud Robotics Core. Please migrate to fix this and unblock the flip of this flag.
(01:13:08) ERROR: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/8f64c2da58aba524c96e00bc4efb6144/external/io_bazel_rules_go/BUILD.bazel:106:10: in go_config rule @io_bazel_rules_go//:go_config: target '@io_bazel_rules_go//go/private:stamp' is not visible from target '@io_bazel_rules_go//:go_config'. Check the visibility declaration of the former target if you think the dependency is legitimate
--
| (01:13:08) ERROR: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/8f64c2da58aba524c96e00bc4efb6144/external/io_bazel_rules_go/BUILD.bazel:106:10: Analysis of target '@io_bazel_rules_go//:go_config' failed
| (01:13:08) ERROR: Analysis of target '//src/go/pkg/synk:go_default_test' failed; build aborted:
keertk
changed the title
Flag --incompatible_config_setting_private_default_visibility will break Cloud Robotics Core in a future Bazel release
Flag --incompatible_config_setting_private_default_visibility will break Cloud Robotics Core in Bazel 7.0
Nov 29, 2022
Incompatible flag
--incompatible_config_setting_private_default_visibility
will be enabled by default in the next major release (Bazel 7.0), thus breaking Cloud Robotics Core. Please migrate to fix this and unblock the flip of this flag.The flag is documented here: bazelbuild/bazel#12933.
Please check the following CI builds for build and test results:
Never heard of incompatible flags before? We have documentation that explains everything.
If you have any questions, please file an issue in https://github.com/bazelbuild/continuous-integration.
The text was updated successfully, but these errors were encountered: