This test is still failing. Looks like super flaky as some run did pass.

Builders failed on: 
- Android Nexus6 WebView Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20WebView%20Perf

- Android One Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf

Looks like collecting the chrome trace fails:
"ChromeTracingStoppedError: Exceptions raised when trying to collect Chrome devtool tracing:
Error when collecting Chrome tracing on devtools at port localabstract:chrome_devtools_remote."

Ned, how are the tracing errors triaged?

Traceback (most recent call last):
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 106, in _RunStoryAndProcessErrorIfNeeded
    test.Measure(state.platform, results)
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py", line 285, in Measure
    trace_result = platform.tracing_controller.StopTracing()
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/core/tracing_controller.py", line 47, in StopTracing
    return self._tracing_controller_backend.StopTracing()
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py", line 140, in StopTracing
    '\n'.join(raised_exception_messages))
TracingException: Exceptions raised when trying to stop tracing:
Traceback (most recent call last):
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py", line 128, in StopTracing
    agent.CollectAgentTraceData(builder)
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py", line 248, in CollectAgentTraceData
    '\n'.join(raised_exception_messages))
ChromeTracingStoppedError: Exceptions raised when trying to collect Chrome devtool tracing:
Error when collecting Chrome tracing on devtools at port localabstract:chrome_devtools_remote:
Traceback (most recent call last):
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py", line 237, in CollectAgentTraceData
    client.CollectChromeTracingData(trace_data_builder)
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/devtools_client_backend.py", line 382, in CollectChromeTracingData
    self._tracing_backend.CollectTraceData(trace_data_builder, timeout)
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/tracing_backend.py", line 235, in CollectTraceData
    self._CollectTracingData(trace_data_builder, timeout)
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/tracing_backend.py", line 263, in _CollectTracingData
    traceback.format_exc())
TracingUnrecoverableException: Exception raised while collecting tracing data:
Traceback (most recent call last):
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/tracing_backend.py", line 256, in _CollectTracingData
    self._inspector_websocket.DispatchNotifications(timeout)
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_websocket.py", line 134, in DispatchNotifications
    self._Receive(timeout)
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_websocket.py", line 149, in _Receive
    data = self._socket.recv()
  File "/b/swarming/w/ir/third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py", line 293, in recv
    opcode, data = self.recv_data()
  File "/b/swarming/w/ir/third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py", line 310, in recv_data
    opcode, frame = self.recv_data_frame(control_frame)
  File "/b/swarming/w/ir/third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py", line 323, in recv_data_frame
    frame = self.recv_frame()
  File "/b/swarming/w/ir/third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py", line 357, in recv_frame
    return self.frame_buffer.recv_frame()
  File "/b/swarming/w/ir/third_party/catapult/telemetry/third_party/websocket-client/websocket/_abnf.py", line 336, in recv_frame
    self.recv_header()
  File "/b/swarming/w/ir/third_party/catapult/telemetry/third_party/websocket-client/websocket/_abnf.py", line 286, in recv_header
    header = self.recv_strict(2)
  File "/b/swarming/w/ir/third_party/catapult/telemetry/third_party/websocket-client/websocket/_abnf.py", line 371, in recv_strict
    bytes_ = self.recv(min(16384, shortage))
  File "/b/swarming/w/ir/third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py", line 427, in _recv
    return recv(self.sock, bufsize)
  File "/b/swarming/w/ir/third_party/catapult/telemetry/third_party/websocket-client/websocket/_socket.py", line 93, in recv
    "Connection is already closed.")
WebSocketConnectionClosedException: Connection is already closed.

Ned, just to be sure that you saw my question in comment #2.

There is no owner of telemetry/chrome tracing? Stack trace suggests that this is an infrastructure issue.

ulan@: we usually assign tracing related error to memory-infra folks: primiano@, erikchen@, hjd@, dskiba@..

I suspect this is a case of tracing size bloat up, hence the time out limit we initially set is not enough.

Upon further investigation, I don't think this is related to v8.browsing_mobile: the same problem is happening in system_health.common_mobile. Unassigning from ulan@.

I'm going to go ahead and disable this on system_health.common_mobile too.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/cc8277f0fd4a626e9db4324a4738a85c5e9fe5cd

commit cc8277f0fd4a626e9db4324a4738a85c5e9fe5cd
Author: Charlie Andrews <charliea@chromium.org>
Date: Fri Jan 05 20:24:04 2018

Disable system_health.common_mobile/tumblr_infinite_scroll

The story has been flaky for a long time now on Android One, and is
already disabled in v8.browsing_mobile.

NOTRY=true
TBR=nednguyen@chromium.org

Bug:  736147 
Change-Id: I1ae06e0cf0a435e4dcf1735ad486d23ea24dadcb
Reviewed-on: https://chromium-review.googlesource.com/852642
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#527369}
[modify] https://crrev.com/cc8277f0fd4a626e9db4324a4738a85c5e9fe5cd/tools/perf/expectations.config

Going to kick off some perf try jobs to see if this is still failing.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12d08f2ea40000

📍 Job complete. See results below.
https://pinpoint-dot-chromeperf.appspot.com/job/12d08f2ea40000

CL is up and going through the CQ now: https://chromium-review.googlesource.com/c/chromium/src/+/1143452

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0fba4dc907589bf2425c43d7e036fc9088a12d8c

commit 0fba4dc907589bf2425c43d7e036fc9088a12d8c
Author: Charlie Andrews <charliea@chromium.org>
Date: Fri Jul 27 19:04:46 2018

Reenable tumblr_infinite_scroll on Android One

Based on a try job in the linked bug, it looks like this story
is now passing.

TBR=sullivan@chromium.org

Bug:  736147 
Change-Id: Icb61a9302213f1351f5bcf86ca2e1d50ab2713e5
Reviewed-on: https://chromium-review.googlesource.com/1143452
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578739}
[modify] https://crrev.com/0fba4dc907589bf2425c43d7e036fc9088a12d8c/tools/perf/expectations.config