Keith Smiley

here's a job that spent >3 minutes cloning the repo https://buildkite.com/bazel/rules-apple-darwin/builds/10261#01964613-6d3e-423b-87b6-fbc49dedbb64 seems like something fishy is going on since this repo is very small

I applied some workarounds here https://github.com/bazelbuild/rules_apple/pull/2679/, notably for this thread i had to delete simulators and setup the visionOS simulator manually. I think this is fine and I can drop...

for a data point on perf, here's a scheduled job that ran all the tests (no caching) before this update in 25 minutes https://buildkite.com/bazel/rules-apple-darwin/builds/10108#01955d8b-1375-4b44-bc54-731e6d05524f my green build before merging these...

I hit what I assume is this same issue but a different set of constraints: ``` ERROR: /private/var/tmp/_bazel_ksmiley/a685f717f9f5cebba0f54a5f41d6fcb3/external/rules_python++python+python_3_13/BUILD.bazel:27:18: Illegal ambiguous match on configurable attribute "actual" in @@rules_python++python+python_3_13//:python_headers: @@rules_python++python+python_3_13//:aarch64-apple-darwin @@rules_python++python+python_3_13//:aarch64-apple-darwin-freethreaded ```

another similar example on linux: ``` ERROR: /home/ubuntu/.cache/bazel/_bazel_ubuntu/df7f5566547a987550d6a5e4980fc00b/external/rules_python++python+python_3_9/BUILD.bazel:19:18: Illegal ambiguous match on configurable attribute "actual" in @@rules_python++python+python_3_9//:py3_runtime: @@rules_python++python+python_3_9//:x86_64-unknown-linux-gnu @@rules_python++python+python_3_9//:x86_64-unknown-linux-musl ```

https://github.com/bazel-contrib/rules_python/issues/2993

I actually hit the original issue here too > A workaround for this is to not use different versions for different target platforms in my case I am using this:...

seems to fix my case of it !

can you rebase? I can merge after

I think as of bazel 7.2.x+ it's ok to check in the lockfile, but previously as Matthieu said this file had a lot of thrash and might change across platforms,...