Log:
[20471:1295:1103/054105:ERROR:gpu_video_decode_accelerator.cc(370)] HW video decode not available for profile 1
  [20471:1295:1103/054105:ERROR:gpu_video_decode_accelerator.cc(370)] HW video decode not available for profile 1
  [20471:1295:1103/054110:ERROR:gpu_video_decode_accelerator.cc(370)] HW video decode not available for profile 1
  [20467:1295:1103/054116:FATAL:synthetic_gesture_target_base.cc(68)] Check failed: PointIsWithinContents(web_wheel.x, web_wheel.y). Mouse wheel position is not within content bounds.
  0   Chromium Framework                  0x000000010c2455f3 _ZN4base5debug10StackTraceC1Ev + 19
  1   Chromium Framework                  0x000000010c25e417 _ZN7logging10LogMessageD2Ev + 71
  2   Chromium Framework                  0x000000010b8a09d7 _ZN7content26SyntheticGestureTargetBase28DispatchInputEventToPlatformERKN5blink13WebInputEventE + 519
  3   Chromium Framework                  0x000000010b8a10bf _ZN7content25SyntheticGestureTargetMac28DispatchInputEventToPlatformERKN5blink13WebInputEventE + 271
  4   Chromium Framework                  0x000000010b8a2536 _ZN7content26SyntheticSmoothMoveGesture28ForwardMouseWheelInputEventsERKN4base9TimeTicksEPNS_22SyntheticGestureTargetE + 534
  5   Chromium Framework                  0x000000010b8a1cb0 _ZN7content26SyntheticSmoothMoveGesture18ForwardInputEventsERKN4base9TimeTicksEPNS_22SyntheticGestureTargetE + 128

This is a failure in the input system. Lan, can you take a look?


Mean while, I will disable this test.

Being disabled https://codereview.chromium.org/2470363002/

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

commit 09d27f4f5495aa9996ab50099c89389f054476aa
Author: mathp <mathp@chromium.org>
Date: Thu Nov 03 13:13:02 2016

[Benchmarks] Disabling twitter benchmark because of flakiness

BUG=662003
TBR=sebsg
NOTRY=true

Review-Url: https://codereview.chromium.org/2470363002
Cr-Commit-Position: refs/heads/master@{#429551}

[modify] https://crrev.com/09d27f4f5495aa9996ab50099c89389f054476aa/tools/perf/benchmarks/system_health_smoke_test.py

Also ":news:flipboard" also seems flaky when I was trying to land my CL:
https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_rel_ng/builds/310155
https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_rel_ng/builds/310203

Thanks for your report, I filed  issue 662021  about news:flipboard flakiness.

Thank you for disabling the test, I will take a look.

nednguyen@google.com, could you please post the full stack of the crash log, thank you?

Sadly this bug was long time, so the log was no available.

+Juan, benchmark owner

Is Lan still the right owner here?

FWIW speed metrics team had really good luck with running a fixit that just had two steps:
1) Run a perf tryjob to enable the story
2) If it succeeds, re-enable and submit.

We re-enabled about 15 stories and only one needed to be disabled again.

Nope, owner should be me.

Indeed I saw the success you had re-enabling stories. Will try to do something similar for memory stories.

Ping! This bug has been flagged as stale by Chrome Speed Metrics bug triage, and it has an owner. Any update on this issue?