Revert of Add buildbot metadata to compiler_proxy log

Revert of Add buildbot metadata to compiler_proxy log (patchset #5 id:80001 of https://codereview.chromium.org/2302453004/ )

Reason for revert:
gsutil.py -h shows help.
https://uberchromegw.corp.google.com/i/tryserver.chromium.linux/builders/linux_chromium_rel_ng/builds/292446/steps/compile%20%28with%20patch%29/logs/stdio

Original issue's description:
> Add buildbot metadata to compiler_proxy log
> 
> We'd like to analyze compiler proxy log. However, buildbot metadata is
> missing, so sometimes hard to determine in which builder the compiler
> proxy log is generated.
> 
> Append buildbot metadata to compiler_proxy log like ninja log.
> 
> Committed: https://chromium.googlesource.com/chromium/tools/build/+/3d1cf68904cab7a23836940d3bdb1f43bee145b8

TBR=phajdan.jr@chromium.org,tikuta@chromium.org,ukai@chromium.org,yyanagisawa@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

Committed: https://chromium.googlesource.com/chromium/tools/build/+/a6f720eeea8f1f50aba71d1d1c27024a406c6ffd

[shinyak, 2016-09-06 07:14:25]

The CQ bit was checked by shinyak@chromium.org

[shinyak, 2016-09-06 07:14:25]

Created Revert of Add buildbot metadata to compiler_proxy log

[commit-bot: I haz the power, 2016-09-06 07:14:28]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-06 07:14:35]

Description was changed from

==========
Revert of Add buildbot metadata to compiler_proxy log (patchset #5 id:80001 of
https://codereview.chromium.org/2302453004/ )

Reason for revert:
gsutil.py -h shows help.
https://uberchromegw.corp.google.com/i/tryserver.chromium.linux/builders/linu...

Original issue's description:
> Add buildbot metadata to compiler_proxy log
> 
> We'd like to analyze compiler proxy log. However, buildbot metadata is
> missing, so sometimes hard to determine in which builder the compiler
> proxy log is generated.
> 
> Append buildbot metadata to compiler_proxy log like ninja log.
> 
> Committed:
https://chromium.googlesource.com/chromium/tools/build/+/3d1cf68904cab7a23836...

TBR=phajdan.jr@chromium.org,tikuta@chromium.org,ukai@chromium.org,yyanagisawa...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
==========

to

==========
Revert of Add buildbot metadata to compiler_proxy log (patchset #5 id:80001 of
https://codereview.chromium.org/2302453004/ )

Reason for revert:
gsutil.py -h shows help.
https://uberchromegw.corp.google.com/i/tryserver.chromium.linux/builders/linu...

Original issue's description:
> Add buildbot metadata to compiler_proxy log
> 
> We'd like to analyze compiler proxy log. However, buildbot metadata is
> missing, so sometimes hard to determine in which builder the compiler
> proxy log is generated.
> 
> Append buildbot metadata to compiler_proxy log like ninja log.
> 
> Committed:
https://chromium.googlesource.com/chromium/tools/build/+/3d1cf68904cab7a23836...

TBR=phajdan.jr@chromium.org,tikuta@chromium.org,ukai@chromium.org,yyanagisawa...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

Committed:
https://chromium.googlesource.com/chromium/tools/build/+/a6f720eeea8f1f50aba7...
==========

[commit-bot: I haz the power, 2016-09-06 07:14:35]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/tools/build/+/a6f720eeea8f1f50aba7...