Description of the bug:
Since 48eb023, using py_test without using rules_python, results in a toolchain error:
ERROR: /Users/brentley/Developer/rules_xcodeproj/tools/params_processors/BUILD:55:8: While resolving toolchains for target //tools/params_processors:swift_debug_settings_processor_tests (ee6eec1): No matching toolchains found for types @@bazel_tools//tools/python:toolchain_type.
Which category does this issue belong to?
Python Rules
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
git checkout https://github.com/MobileNativeFoundation/rules_xcodeproj.git
cd rules_xcodeproj
USE_BAZEL_VERSION=last_green bazelisk build --nobuild //tools/params_processors:swift_debug_settings_processor_tests
Which operating system are you running Bazel on?
macOS 14.1.1
What is the output of bazel info release?
No response
If bazel info release returns development version or (@non-git), tell us how you built Bazel.
No response
What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?
No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
48eb023
Have you found anything relevant by searching the web?
#20315
Any other information, logs, or outputs that you want to share?
No response
Description of the bug:
Since 48eb023, using
py_testwithout usingrules_python, results in a toolchain error:Which category does this issue belong to?
Python Rules
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Which operating system are you running Bazel on?
macOS 14.1.1
What is the output of
bazel info release?No response
If
bazel info releasereturnsdevelopment versionor(@non-git), tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD?No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
48eb023
Have you found anything relevant by searching the web?
#20315
Any other information, logs, or outputs that you want to share?
No response