John, did you check whether these tests are running successfully on other Android devices?

May be due to a failure to pass --disable-gesture-requirement-for-media-playback successfully to the browser. See https://github.com/catapult-project/catapult/issues/3122 .

Can we suppress this failure for the moment?

I'll try to suppress it. I haven't see any flakes on any other android devices (since the test was fixed), so it's possible this is an actual driver bug.

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

commit 65790e805f1e91700e63a2d47fa960105f13648d
Author: jbauman <jbauman@chromium.org>
Date: Sat Apr 29 00:23:21 2017

Mark Pixel_Video_MP4 flaky on NVIDIA android.

It's currently flaking on the NVIDIA Shield TV.

BUG=716564
TBR=kbr@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

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

[modify] https://crrev.com/65790e805f1e91700e63a2d47fa960105f13648d/content/test/gpu/gpu_tests/pixel_expectations.py

do we usually get traces when running this test?

I don't think so. What command line flags should be passed to Telemetry to generate something useful for debugging?

+ned, any ideas on how to query Chrome for the command line flags from within Telemetry?

There is no devtool protocol. For now, I suggest do:
browser.platform.tracing_controller.Start()
trace_data = browser.platform.tracing_controller.Stop()
model = model_module.TimelineModel(trace_data)
print model.metadata

* Maybe the model.metadata needs some fix up for the flag part, I am not sure (https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/telemetry/timeline/trace_event_importer.py?rcl=18b10cbe616e114d9eae4e7a0dd07c8d81a7ef39&l=166)

I'm adding the command line to Telemetry's debugging output in  Issue 718635 .

The browser's command line is now in Telemetry's debug output per  Issue 718635 .

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot