[Bazel CI]Test Failure: local_toolchains_test fails with "bazel: command not found" (Exit 127) - "bazel_self" integration test failure

[deepalak56]

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/5230#019be3f2-f5b9-4c77-a78f-b4cf3381be2a

Platform: Windows, MacOs

Logs:

(04:25:45) FAIL: //tests/integration:local_toolchains_test_bazel_self (Exit 127) (see C:/b/yss4weqk/execroot/_main/bazel-out/x64_windows-fastbuild/testlogs/tests/integration/local_toolchains_test_bazel_self/test_attempts/attempt_1.log)
--
(04:25:45) FAIL: //tests/integration:local_toolchains_test_bazel_self (Exit 127) (see C:/b/yss4weqk/execroot/_main/bazel-out/x64_windows-fastbuild/testlogs/tests/integration/local_toolchains_test_bazel_self/test_attempts/attempt_2.log)
(04:25:45) [7 / 8] Testing //tests/integration:local_toolchains_test_bazel_self; 0s local, remote-cache
buildkite-agent artifact upload --content-type text/plain;charset=utf-8 tests\integration\local_toolchains_test_bazel_self\test_attempts\attempt_1.log
2026-01-22 04:25:45 WARN   The git-mirrors experiment has been promoted to a stable feature in agent version v3.47.0. You can safely remove the `--experiment git-mirrors` flag to silence this message and continue using the feature
2026-01-22 04:25:45 INFO   Found 1 files that match "tests\\integration\\local_toolchains_test_bazel_self\\test_attempts\\attempt_1.log"
2026-01-22 04:25:45 INFO   Uploading to Google Cloud Storage ("gs://bazel-untrusted-buildkite-artifacts/019be3f2-f5b9-4c77-a78f-b4cf3381be2a"), using your agent configuration
(04:25:45) FAIL: //tests/integration:local_toolchains_test_bazel_self (Exit 127) (see C:/b/yss4weqk/execroot/_main/bazel-out/x64_windows-fastbuild/testlogs/tests/integration/local_toolchains_test_bazel_self/test.log)
 
FAILED: //tests/integration:local_toolchains_test_bazel_self (Summary)
C:/b/yss4weqk/execroot/_main/bazel-out/x64_windows-fastbuild/testlogs/tests/integration/local_toolchains_test_bazel_self/test.log
C:/b/yss4weqk/execroot/_main/bazel-out/x64_windows-fastbuild/testlogs/tests/integration/local_toolchains_test_bazel_self/test_attempts/attempt_1.log
C:/b/yss4weqk/execroot/_main/bazel-out/x64_windows-fastbuild/testlogs/tests/integration/local_toolchains_test_bazel_self/test_attempts/attempt_2.log
(04:25:45) INFO: From Testing //tests/integration:local_toolchains_test_bazel_self:
==================== Test output for //tests/integration:local_toolchains_test_bazel_self:
/c/b/yss4weqk/execroot/_main/bazel-out/x64_windows-fastbuild/bin/tests/integration/local_toolchains_test_bazel_self.exe.runfiles/_main/../rules_bazel_integration_test++bazel_binaries+build_bazel_bazel_self/bazel: line 6: bazel: command not found

Culprit: bazelbuild/bazel@68d80e7

Steps:

git clone https://github.com/buchgr/bazel-remote
git reset 889e5acd350e584c23d5c770c3b42eaa86c8e240 --hard
export USE_BAZEL_VERSION=68d80e7f63ef4df8d541e9d87ed9adaa47b73c7e
bazel test --build_tag_filters=integration-test --test_env=LocalAppData --test_env=BAZELISK_USER_AGENT --test_env=USE_BAZEL_VERSION --lockfile_mode=off //tests/integration:local_toolchains_test_bazel_self

CC Greenteam @Wyverald

[deepalak56]

As per artifacts, it seems like the wrapper script can't find any Bazel and looks like a bug within the rules_bazel_integration_test configuration.