[Bazel CI] Bazel build fails with "no such attribute 'exec_tools' in 'genrule' rule" on x86_64

[sgowroji]

CI: https://buildkite.com/bazel/bazel-at-head-plus-disabled/builds/2004#018eb729-4657-4033-b740-d140f90789ba

Platform: Ubuntu

Logs:

ERROR: [0m/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/4fb9d7987f8ae1a75d16107452f22764/external/com_google_protobuf/src/google/protobuf/compiler/BUILD.bazel:140:13: @@com_google_protobuf//src/google/protobuf/compiler:protoc_aarch64_test_genrule: no such attribute 'exec_tools' in 'genrule' rule (did you mean 'executable'?)
ERROR: [0m/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/4fb9d7987f8ae1a75d16107452f22764/external/com_google_protobuf/src/google/protobuf/compiler/BUILD.bazel:145:12: @@com_google_protobuf//src/google/protobuf/compiler:protoc_x86_64_test_genrule: no such attribute 'exec_tools' in 'genrule' rule (did you mean 'executable'?)
ERROR: [0m/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/4fb9d7987f8ae1a75d16107452f22764/external/com_google_protobuf/src/google/protobuf/compiler/BUILD.bazel:27:11: Cannot compute config conditions
ERROR: [0m/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/4fb9d7987f8ae1a75d16107452f22764/external/com_google_protobuf/BUILD.bazel:275:11: Target '@@com_google_protobuf//src/google/protobuf/compiler:importer' contains an error and its package is in error and referenced by '@@com_google_protobuf//:protobuf'
ERROR: [0mAnalysis of target '//test/integration:typed_metadata_integration_test' failed; build aborted: Analysis failed

Culprit:

Steps:

git clone https://github.com/envoyproxy/envoy
git reset 56b19101483c5d3dc37aaf72b43b7acc9bc24f44  --hard
export USE_BAZEL_VERSION=3f9d80c35d88a280c2d53682f3d201b4733a3fff
bazel test  //test/common/common/... //test/integration/... //test/exe/... 

CC Greenteam @meteorcloudy

[sgowroji]

CC @alyssawilk

[phlax]

@sgowroji i think the bazel version you are using no longer accepts exec_tools - these need to be updated to tools iirc

i think we have already fixed these in Envoy - certainly there are none in the repo when grepping - so wondering where this is coming from

[phlax]

ah - in protobuf i think - my guess is that we will need to update protobuf before we can update bazel (amongst many other things)

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.

[sgowroji]

Not stale