-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Bazel CI: Downstream projects broken due to the change to StarlarkToolchainContext #13320
Comments
cc @katre |
Thanks for the quick fix! |
Bazel auto-sheriff is convinced that the culprit here also caused this very different error: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1990#284aa31e-ee16-447a-af9f-7a30606fc5a5 |
There shouldn't be any behavior changes (after b120d4f), but I will investigate. |
I wonder whether ebac27e is the actual culprit, based on the commit message. |
I can reproduce the error with bazel at head, and it goes away when I run with |
John, thanks for testing! I discovered another GitHub issue that I hadn't noticed before. Sorry for the noise. |
Fixes bazelbuild#13320. PiperOrigin-RevId: 367624002
https://buildkite.com/bazel/bazel-auto-sheriff-face-with-cowboy-hat/builds/486
Caused by 627c16e.
rules_docker:
rules_go:
rules_jvm_external:
rules_webtesting:
The text was updated successfully, but these errors were encountered: