-
Notifications
You must be signed in to change notification settings - Fork 122
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
Flag --incompatible_disable_starlark_host_transitions will break Flogger in Bazel 7.0 #326
Comments
I'm not sure what action I need to take here, or even what the issue is exactly. I look at that CI build and see Flogger passing. |
I don't see anything about this in the docs, but it looks like the "Running Bazel with all incompatible flags" section may be the one to look at:
So presumably we need to fix it in bazel-common, similar to google/bazel-common#97 and google/bazel-common#37. |
Ah, right, forgot about bazel-common. |
Ok, already fixed in bazel-common: google/bazel-common@b89cd87 Need to update the version Flogger's using, then. |
Fixes #326. RELNOTES=n/a PiperOrigin-RevId: 495950468
Hi @cgdecker thanks for looking into this!
|
Hi @cgdecker, This Error is still persists in the latest CI . Can you please reopen it.
|
Incompatible flag
--incompatible_disable_starlark_host_transitions
will be enabled by default in the next major release (Bazel 7.0), thus breaking Flogger. Please migrate to fix this and unblock the flip of this flag.The flag is documented here: bazelbuild/bazel#17032.
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: