This is affecting Nexus5x and Nexus7v2

=>watk, looks like your change is having some trouble.

robertocn@, what are those revision numbers you gave? They're not Cr-Commit-Position numbers because those correspond to 2010 commits. I'm confused.

Anyway, this is the first failing build: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20Perf%20%282%29/builds/3113

It included: 

commit b4f0e124c5a8884a16459c67d956d011be8acc5a
Author: crouleau <crouleau@chromium.org>

    Re-enable media.android.tough_video_cases.

Also, it's the reference build that's failing. i.e., it's running an old stable release of Chrome, so it couldn't be caused by my change AFAIK. I don't know how to check what the reference build is. robertocn@?

Apparently you look here: https://cs.chromium.org/chromium/src/third_party/catapult/common/py_utils/py_utils/chrome_binaries.json?type=cs&q=catapult/common/py_utils/py_utils/chrome_binaries.json&sq=package:chromium&l=1

And the answer is M56.

The commit that allowed us to reenable tough_video_cases landed in 57. So that explains why the reference build fails; it doesn't have the fix.

We're actually working on just showing the ref build as green in  bug 680138 , because there isn't much we can do when it fails. I actually think we should WontFix of block on that bug.