Error No matching toolchains found for types @@bazel_tools//tools/python:toolchain_type in Downstream CI with 7.1

[sgowroji]

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3657#018da594-7593-4e8f-850f-187a1a4cb063

Platform: Windows, MacOS, Ubuntu

Logs:

(03:07:01) ERROR: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/dd5f1ab0fb45f70a5ca8f71a165f3850/external/bazel_tools/tools/jdk/BUILD:133:10: While resolving toolchains for target @@bazel_tools//tools/jdk:proguard_whitelister (102280f): No matching toolchains found for types @@bazel_tools//tools/python:toolchain_type.
To debug, rerun with --toolchain_resolution_debug='@@bazel_tools//tools/python:toolchain_type'

CC Greenteam @mai93 @meteorcloudy 

List of Downstream projects failing with above error logs

1. Stardoc
2. rules_apple
3. rules_dotnet
4. rules_proto
5. Bazel skylib

[meteorcloudy]

Can you use bazelisk to bisect those failures?

[sgowroji]

I tried this '''
bazelisk --bisect=f9acae2b1f486c74f7b465b11e18d8d8d1ed410e..3e17028 build //src:bazel //src:bazel_jdk_minimal //src:test_repos //src/main/java/...'''. It was succeeded,And didn't resulted any culprit.

[meteorcloudy]

@sgowroji You should bisect the broken downstream project, not building Bazel itself.

pcloudy@pcloudy-macbookpro3:~/workspace/bazel-skylib (main)
$ bazel --bisect=7.0.0..release-7.1.0 build //...

[meteorcloudy]

And the result is

--- Bisect Result

first bad commit is https:/bazelbuild/bazel/commit/86a5f6b66dac4001c88fa00f938e0b482aede4a7

[meteorcloudy]

OK, probably we need to backport 9810870

[sgowroji]

Yes

--- Succeeded at 1821a88

--- Bisect Result

first bad commit is 86a5f6b
sgowroji-macbookpro3:bazel-skylib sgowroji$

[iancha1992]

Fixed by #21369