tree 42f6e240c5d42f1d9fcb10f93339a8864fb134a6
parent ed8b09a8efbdcfb110cf857bd1b41927ea6306cb
author Philipp Wollermann <philwo@google.com> 1580213382 -0800
committer Philipp Wollermann <philwo@google.com> 1581588295 +0100

Do not fail or print errors when Shellzelisk cannot find a requested ?

?Bazel binary, if tools/bazel exists.

Instead, we should do our best to populate the $BAZEL_REAL env var with some meaningful path, but then delegate to tools/bazel without aborting or printing anything, in case we couldn't find a requested binary or make sense of the contents of .bazelversion.

This is in response to https://github.com/bazelbuild/bazel/issues/10356#issuecomment-576386798 and hopefully fixes the use case reported by the affected users.

@laurentlb This is the cherry-pick I mentioned. I will import it, if you LGTM this PR.
@Helcaraxan @davido FYI.

Closes #10664.

PiperOrigin-RevId: 291904662