Yun Peng

Can you please add a new `RELNOTES[New]: ` tag in the PR description?

FYI @kotlaja I ran a compatibility test with the top 100 BCR modules for `--incompatible_auto_exec_groups` with Bazel 7.4.1, here is the result: https://buildkite.com/bazel/bcr-bazel-compatibility-test/builds/45

Our postsubmit is green for release-7.1.0: https://buildkite.com/bazel/bazel-bazel/builds/27092#_ > OTHER_ARGS='--macos_minimum_os=10.11 --host_cxxopt='-Wno-deprecated-declarations' --host_cxxopt='-Wno-deprecated-builtins'' > bazel build //src:bazel --java_runtime_version=remotejdk_11 $OTHER_ARGS And I couldn't reproduce the issue with on a Mac machine. This is...

Maybe you can explicitly specify the toolchain with `--extra_toolchains`, it should take priority. The toolchains register by bazel_dep respect a BFS order.

@brentleyjones Can you provide the steps to reproduce this?

Sure, feel free to send a PR!

@fmeum Thanks, that's a good point, and we do have [--experimental_scale_timeouts](https://bazel.build/reference/command-line-reference#common_options-flag--experimental_scale_timeouts), which might be a better fit to work around the issue? @Bechir-Braham

OK, that flag controls the `repository_ctx.execute` timeout, the one controls http download timeout is [--http_timeout_scaling](https://bazel.build/reference/command-line-reference#common_options-flag--http_timeout_scaling)

> "could not resolve the version " issue is from Bazelisk Can we retry in Bazelisk for such errors?

I assume this affects all CI pipeline? Can we somehow give a notice to CI users?