Revert of Reland 'Add buildbot metadata to compiler_proxy log'

Revert of Reland 'Add buildbot metadata to compiler_proxy log' (patchset #2 id:20001 of https://codereview.chromium.org/2311123002/ )

Reason for revert:
-h still not working: ArgumentException: Invalid header specifed

Original issue's description:
> Reland '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.
> 
> The difference from the previous patch is to add '--' to gsutil.py.
> Without '--', gsutil.py consumes options which is expected to pass
> to gsutil itself.
> 
> Committed: https://chromium.googlesource.com/chromium/tools/build/+/3437df739c975cec15fe81d6adfed5c0fbdf2c6c

TBR=yyanagisawa@chromium.org,ukai@chromium.org,tikuta@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/+/edd1455b5b82f864701dcbf581aa0b7011ecb98e

[shinyak, 2016-09-06 08:46:23]

The CQ bit was checked by shinyak@chromium.org

[shinyak, 2016-09-06 08:46:23]

Created Revert of Reland 'Add buildbot metadata to compiler_proxy log'

[commit-bot: I haz the power, 2016-09-06 08:46:30]

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 08:46:34]

Description was changed from

==========
Revert of Reland 'Add buildbot metadata to compiler_proxy log' (patchset #2
id:20001 of https://codereview.chromium.org/2311123002/ )

Reason for revert:
-h still not working: ArgumentException: Invalid header specifed

Original issue's description:
> Reland '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.
> 
> The difference from the previous patch is to add '--' to gsutil.py.
> Without '--', gsutil.py consumes options which is expected to pass
> to gsutil itself.
> 
> Committed:
https://chromium.googlesource.com/chromium/tools/build/+/3437df739c975cec15fe...

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

to

==========
Revert of Reland 'Add buildbot metadata to compiler_proxy log' (patchset #2
id:20001 of https://codereview.chromium.org/2311123002/ )

Reason for revert:
-h still not working: ArgumentException: Invalid header specifed

Original issue's description:
> Reland '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.
> 
> The difference from the previous patch is to add '--' to gsutil.py.
> Without '--', gsutil.py consumes options which is expected to pass
> to gsutil itself.
> 
> Committed:
https://chromium.googlesource.com/chromium/tools/build/+/3437df739c975cec15fe...

TBR=yyanagisawa@chromium.org,ukai@chromium.org,tikuta@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/+/edd1455b5b82f864701d...
==========

[commit-bot: I haz the power, 2016-09-06 08:46:36]

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