//src/test/shell/bazel:srcs_test failed to build on Intel macOS due to local_bazel_source_list

[meteorcloudy]

Description of the bug:

https://buildkite.com/bazel/bazel-bazel/builds/26996#018de4f2-93fd-4253-b7ad-0c990cbb3765

(11:57:23) ERROR: /private/var/tmp/_bazel_buildkite/42e36ea1c1dcd25f4ab5af8d98bf3465/external/_main~bazel_test_deps~local_bazel_source_list/BUILD:2:8: Executing genrule @@_main~bazel_test_deps~local_bazel_source_list//:sources failed: (Exit 1): bash failed: error executing Genrule command (from target @@_main~bazel_test_deps~local_bazel_source_list//:sources)
  (cd /private/var/tmp/_bazel_buildkite/42e36ea1c1dcd25f4ab5af8d98bf3465/sandbox/darwin-sandbox/8920/execroot/_main && \
  exec env - \
    PATH=/Users/buildkite/Library/Caches/bazelisk/downloads/sha256/0a9bfb9581a37049b7dcf204cc569b0458bedba20e84c55c0952161e036525ba/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin \
  /bin/bash -c 'source external/bazel_tools/tools/genrule/genrule-setup.sh; cat external/_main~bazel_test_deps~local_bazel_source_list/find.result.raw | grep -Ev '\''^(\.git|.ijwb|out/|output/|bazel-|derived|tools/defaults/BUILD)'\'' | grep -Ev '\''XXXXXXXXXXXXXX1268778dfsdf4'\'' | sort -u > bazel-out/darwin_x86_64-fastbuild/bin/external/_main~bazel_test_deps~local_bazel_source_list/sources.txt')
# Configuration: c1e7f9352bff897263fedb8c095e0afd372722603f37668d6a04cdf8ec4bda5f
# Execution platform: //:default_host_platform
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging

Which category does this issue belong to?

No response

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

This seems to be only reproducible on Intel macOS machines on CI.

Which operating system are you running Bazel on?

macOS (Intel)

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 HEAD ?

No response

Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response