tree cff815d3111135b34db0b374b3bb20134b10b9f5
parent 29b0cda8e40810988d314a491162501e6875d3e5
author davg <davg@google.com> 1534975574 -0400
committer David Goldman <davg@google.com> 1535042817 -0400

Improve error messages for early Bazel failures

Tulsi previously only used stdout/stderr from Bazel's BEP during builds
inside of the IDE. This is of course problematic for Bazel failures
which occur before BEP can be initialized.

As a workaround, if we are unable to read any build events via BEP, we
output Bazel's stdout/stderr directly.

This change also makes the error messages a bit more useful by pointing
Xcode to the bazel_build.py script, so the user has more insight into
errors generated by our script.

PiperOrigin-RevId: 209837296