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

commit 5b1b3be73f1966599c991575cc9108ec3fc1a5a6
Author: Stephen Martinis <martiniss@chromium.org>
Date: Fri Jun 23 23:56:29 2017

Disable stories for blink_perf.shadow_dom

Some stories are failing on the Android One perf bot.

TBR=nednguyen

Bug:  736512 
Change-Id: Ic77a5f130008313399dc5bec0a0b8da3ac6ef932
Reviewed-on: https://chromium-review.googlesource.com/546942
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#482078}
[modify] https://crrev.com/5b1b3be73f1966599c991575cc9108ec3fc1a5a6/tools/perf/benchmarks/blink_perf.py

cc: nednguyen for advice.


I can see the following message from the log.

Is there any time out limit in running performance tests? If so, I have to make these tests more faster (e.g. reducing the number of loops).


  File "/b/swarming/w/ir/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py", line 443, in _HandleInspectorDomainNotification
    raise exception
DevtoolsTargetCrashException: Devtools target crashed
********************************************************************************
(/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:496 _AddDebuggingInformation) Received a socket error in the browser connection and the tab still exists. The operation probably timed out.

Error message says "there is a socket error in the browser connection and the tab still exists." So this is more like a failure in devtool connection and not about the speed of the test to me. 

Thanks. Let me enable this test again.

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

commit 8ace7ae1cf681a471d217ca3dfc2627d8e719ca9
Author: Hayato Ito <hayato@chromium.org>
Date: Thu Sep 07 01:55:33 2017

Enable stories for blink_perf.shadow_dom

These stories were disabled at r482078, however, that is more like a failure in
devtool connection devtools, as per
https://bugs.chromium.org/p/chromium/issues/detail?id=736512#c5.

Let's enable these stories and see what's going on.

Bug:  736512 
Change-Id: Ib829b3716a5abb104ec8e7954d7e935c55fe768f
Reviewed-on: https://chromium-review.googlesource.com/652006
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#500181}
[modify] https://crrev.com/8ace7ae1cf681a471d217ca3dfc2627d8e719ca9/tools/perf/benchmarks/blink_perf.py