aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/main/java/com/google/devtools/build/lib/runtime/CommandExecutor.java
diff options
context:
space:
mode:
authorGravatar Klaus Aehlig <aehlig@google.com>2017-06-28 11:18:40 +0200
committerGravatar Marcel Hlopko <hlopko@google.com>2017-06-28 15:25:38 +0200
commit0a0d7a48095a893efe41a6e54deb57f47d750594 (patch)
tree977c578abcfaa41a29e44eddd09f816768a3a99a /src/main/java/com/google/devtools/build/lib/runtime/CommandExecutor.java
parentfe037f36edcf2a57a3db601b8f71771260336c1b (diff)
BugReport: include ERROR on internal error messages
While a sentence like "bazel ran out of memory and crashed" should be human-readable enough, it seems that users often only scan for the word ERROR in the output and assume everything is fine, if it doesn't occur. Things get worse, if that procedure is scripted. While these kind of behaviors should be discouraged, mitigate the consequences by providing mainstream error messages. Change-Id: I5a032360881c53575bfbd37a471b96933622d3c5 PiperOrigin-RevId: 160385223
Diffstat (limited to 'src/main/java/com/google/devtools/build/lib/runtime/CommandExecutor.java')
0 files changed, 0 insertions, 0 deletions