It's been failing since it was enabled. The reference build should be updated soon, which will hopefully fix this.

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

commit b77a137cf1723290b1286045d06b601f77e804be
Author: alexandermont <alexandermont@chromium.org>
Date: Tue Aug 23 02:57:41 2016

Disable top_10_mobile_memory test on reference build.

This test is working on current build and so will pass ass soon
as the reference build is rolled.

BUG= chromium:639007 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq

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

[modify] https://crrev.com/b77a137cf1723290b1286045d06b601f77e804be/tools/perf/benchmarks/v8.py

This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.