[Telemetry] Suppress red-herring error messages.

[Telemetry] Suppress red-herring error messages.

These confuse sheriffs in the log because they are harmless and
just mean that the browser closed the connection to the webserver
aburptly.

WPR has the same logic here:
https://github.com/chromium/web-page-replay/blob/master/httpproxy.py

This eliminates this stack:
Traceback (most recent call last):
  File "/usr/lib/python2.7/SocketServer.py", line 593, in process_request_thread
    self.finish_request(request, client_address)
  File "/usr/lib/python2.7/SocketServer.py", line 334, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib/python2.7/SocketServer.py", line 649, in __init__
    self.handle()
  File "/usr/lib/python2.7/BaseHTTPServer.py", line 342, in handle
    self.handle_one_request()
  File "/usr/lib/python2.7/BaseHTTPServer.py", line 310, in handle_one_request
    self.raw_requestline = self.rfile.readline(65537)
  File "/usr/lib/python2.7/socket.py", line 476, in readline
    data = self._sock.recv(self._rbufsize)
error: [Errno 104] Connection reset by peer

BUG=

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=290948

[tonyg, 2014-07-11 20:12:58]

https://codereview.chromium.org/386963006/diff/1/tools/telemetry/telemetry/co...
File tools/telemetry/telemetry/core/memory_cache_http_server.py (right):

https://codereview.chromium.org/386963006/diff/1/tools/telemetry/telemetry/co...
tools/telemetry/telemetry/core/memory_cache_http_server.py:31: def handle(self):
This is a copy from BaseHTTPServer with the try-except block added. I'd love to
figure out a way to catch that exception without overriding this. But
unfortunately, I don't see any Telemetry code in the stack. Ideas?

[dtu, 2014-07-11 20:17:34]

https://codereview.chromium.org/386963006/diff/1/tools/telemetry/telemetry/co...
File tools/telemetry/telemetry/core/memory_cache_http_server.py (right):

https://codereview.chromium.org/386963006/diff/1/tools/telemetry/telemetry/co...
tools/telemetry/telemetry/core/memory_cache_http_server.py:31: def handle(self):
On 2014/07/11 20:12:58, tonyg wrote:
> This is a copy from BaseHTTPServer with the try-except block added. I'd love
to
> figure out a way to catch that exception without overriding this. But
> unfortunately, I don't see any Telemetry code in the stack. Ideas?

Just call super.handle().

[tonyg, 2014-07-11 20:36:09]

On 2014/07/11 20:17:34, dtu wrote:
>
https://codereview.chromium.org/386963006/diff/1/tools/telemetry/telemetry/co...
> File tools/telemetry/telemetry/core/memory_cache_http_server.py (right):
> 
>
https://codereview.chromium.org/386963006/diff/1/tools/telemetry/telemetry/co...
> tools/telemetry/telemetry/core/memory_cache_http_server.py:31: def
handle(self):
> On 2014/07/11 20:12:58, tonyg wrote:
> > This is a copy from BaseHTTPServer with the try-except block added. I'd love
> to
> > figure out a way to catch that exception without overriding this. But
> > unfortunately, I don't see any Telemetry code in the stack. Ideas?
> 
> Just call super.handle().

D'oh, thanks :)

super(MemoryCacheHTTPRequestHandler, self).handle() doesn't work. I think
because SimpleHTTPRequestHandler doesn't override handle(). So I called
BaseHTTPRequestHandler directly.

[tonyg, 2014-07-28 15:53:30]

Friendly ping

[dtu, 2014-07-29 19:02:11]

lgtm

[dtu, 2014-07-29 19:02:31]

On 2014/07/29 19:02:11, dtu wrote:
> lgtm

Got a reason why it's BaseHTTPRequestHandler instead of super?

[tonyg, 2014-07-29 19:04:47]

On 2014/07/29 19:02:31, dtu wrote:
> On 2014/07/29 19:02:11, dtu wrote:
> > lgtm
> 
> Got a reason why it's BaseHTTPRequestHandler instead of super?

super(MemoryCacheHTTPRequestHandler, self).handle() doesn't work. I think
because SimpleHTTPRequestHandler doesn't override handle(). So I called
BaseHTTPRequestHandler directly.

[tonyg, 2014-07-29 21:29:21]

The CQ bit was checked by tonyg@chromium.org

[commit-bot: I haz the power, 2014-07-29 21:31:11]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/tonyg@chromium.org/386963006/20001

[commit-bot: I haz the power, 2014-07-30 03:24:41]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_chromium_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel/...)
  win_chromium_x64_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[commit-bot: I haz the power, 2014-07-30 04:39:09]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-07-30 04:39:09]

Try jobs failed on following builders:
  win_chromium_x64_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[tonyg, 2014-08-14 04:13:43]

The CQ bit was checked by tonyg@chromium.org

[commit-bot: I haz the power, 2014-08-14 04:18:13]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/tonyg@chromium.org/386963006/20001

[commit-bot: I haz the power, 2014-08-14 06:26:34]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  linux_chromium_chromeos_rel_swarming on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  mac_chromium_rel_swarming on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
  win_chromium_rel_swarming on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
  win_chromium_x64_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[commit-bot: I haz the power, 2014-08-14 06:31:07]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-08-14 06:31:08]

Try jobs failed on following builders:
  mac_chromium_rel_swarming on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
  win_chromium_x64_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[tonyg, 2014-08-20 18:27:37]

The CQ bit was checked by tonyg@chromium.org

[commit-bot: I haz the power, 2014-08-20 18:28:51]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/tonyg@chromium.org/386963006/40001

[commit-bot: I haz the power, 2014-08-20 21:58:15]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_chromium_x64_rel_swarming on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[commit-bot: I haz the power, 2014-08-20 23:39:56]

Committed patchset #3 (40001) as 290948