-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Update rules_foreign_cc #13943
Comments
cc @benjaminp @lizan I'm not sure what's causing the problem you describe. The https://github.com/bazelbuild/rules_foreign_cc was updated to the most recent change in that repo 14 days ago thank to #13758 |
I think it's because this has been red for a few weeks: https://buildkite.com/bazel/envoy |
The buildkite pipeline is failing to pull the docker image @philwo, any ideas? |
@Wyverald Can you quote the error message and link to a job where the error can be seen? I had a quick look at Buildkite from my phone but couldn’t see anything pointing to Docker. |
https://buildkite.com/bazel/envoy/builds/1360#f0b7d037-077d-46c6-bb67-6aafecb8617a
|
@benjaminp @philwo looking at the bazel CI failure and last green, the reason that RBE is failing is because we started use multipool and that isn't match what bazelci does. We have a couple of large machines labeled
A short-term fix will be exclude those build target from bazel-ci. |
Envoy is failing after a flag flip which affects rules_foreign_cc
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1752#1430dbb5-ec1d-4fff-9394-3d623f259aff
The flag flip went in here:
bazelbuild/bazel@9a2893d
The description of the incompatible change is here:
bazelbuild/bazel#10860
Envoy is not using the API, all that's needed here is to update to the most recent version of rules_foreign_cc.
The text was updated successfully, but these errors were encountered: