[Bazel CI] Error While resolving toolchains for target //tests/base_rules/py_test. No matching toolchains found for types.

[sgowroji]

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4641#01968ee3-034a-44a1-9599-541d19ea7f77

Platform: Ubuntu, MacOS, Debian

Logs:

ERROR: �[0m/var/lib/buildkite-agent/builds/bk-docker-vfmd/bazel-org-repo-root/rules_python/tests/base_rules/py_test/BUILD.bazel:18:19: While resolving toolchains for target //tests/base_rules/py_test:test_basic_windows_subject (b27383e): No matching toolchains found for types:
ERROR: �[0m/var/lib/buildkite-agent/builds/bk-docker-vfmd/bazel-org-repo-root/rules_python/tests/base_rules/py_test/BUILD.bazel:18:19: While resolving toolchains for target //tests/base_rules/py_test:test_mac_requires_darwin_for_execution_subject (8444979): No matching toolchains found for types:

Steps:

git clone https://github.com/bazelbuild/rules_python
git reset ea80366b29219d3dad8c90191c21b77a4525875a  --hard
export USE_BAZEL_VERSION=0b5216ffe029b5fb0d0090f15fc4781522aac6d3
bazel build  ... @rules_python//examples/wheel/... 

CC Greenteam @meteorcloudy

[rickeylev]

No matching toolchains found for types:
  @@bazel_tools//tools/test:default_test_toolchain_type: By default, tests are executed on the first execution platform that matches all constraints specified by the target platform. Either register the target platform (or a platform with at least the same constraints) as an execution platform, or override the default behavior by registering a custom toolchain for @bazel_tools//tools/test:default_test_toolchain_type.

We have some analysis tests that force the platform to windows/mac in order to test the windows code paths. Here's one of the failing ones mentioned in the error:

https://github.com/bazel-contrib/rules_python/blob/main/tests/base_rules/py_test/py_test_tests.bzl#L41

It sets config_settings:

 "//command_line_option:cpu": "darwin_x86_64",
 "//command_line_option:crosstool_top": CROSSTOOL_TOP,
 "//command_line_option:extra_toolchains": CC_TOOLCHAIN,
 "//command_line_option:platforms": [MAC_X86_64],

Where cc toolchain and crosstool are set to an no-op impl. Platforms is shown below.

I'm guessing either the "default_test_toolchain_type" Bazel sets up is misconfigured, the config state those tests enter isn't quite valid, or the custom platform definition used for the test isn't quite valid.

Here's the basic mac platform it uses: https://github.com/bazel-contrib/rules_python/blob/main/tests/support/BUILD.bazel#L27

platform(
    name = "mac",
    constraint_values = [
        "@platforms//os:macos",
    ],
)

@katre @gregestren -- Would one of you know about the "default test" toolchain type and/or if the config state/platform the test are switching to is correct?

[meteorcloudy]

https://buildkite.com/bazel/bazel-auto-sheriff-face-with-cowboy-hat/builds/2002 identifies bazelbuild/bazel@2780393 as the culprit.

/cc @fmeum

[fmeum]

I will send a fix soon.

[fmeum]

Sent #2861

[sgowroji]

@fmeum Error still exists in Downstream CI https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4652#0196a3c6-540e-4e81-a7f3-00fe72ccebf3

[fmeum]

@sgowroji The downstream run you linked checked out rules_python at ea80366, which is from mid March.

Cc @meteorcloudy

[sgowroji]

@fmeum Sorry for the confusion. Thanks for pointing me about the commit.

[sgowroji]

@fmeum I noticed for latest commit on windows and macos , Still this is failling
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4663#0196b339-9cc1-43de-9576-d837e582524a
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4663#0196b339-9cc2-4828-8631-8db1f60d7903

CC @meteorcloudy

[meteorcloudy]

ERROR: /Users/buildkite/builds/bk-macos-intel-j9ut/bazel-org-repo-root/rules_python/tests/base_rules/py_test/BUILD.bazel:18:19: While resolving toolchains for target //tests/base_rules/py_test:test_main_module_bootstrap_script_subject (6f4ee0f): No matching toolchains found for types:
  @@bazel_tools//tools/test:default_test_toolchain_type: By default, tests are executed on the first execution platform that matches all constraints specified by the target platform. Either register the target platform (or a platform with at least the same constraints) as an execution platform, or override the default behavior by registering a custom toolchain for @bazel_tools//tools/test:default_test_toolchain_type.
To debug, rerun with --toolchain_resolution_debug='@@bazel_tools//tools/test:default_test_toolchain_type'
For more information on platforms or toolchains see https://bazel.build/concepts/platforms-intro.

@fmeum Something else is missing?

[fmeum]

I can't reproduce the failure locally, but #2869 should fix this.