Disable image decoding perf test for android

As chrome on android starts to use deferred image decoding, images decoding may not be captured by InspectorTimelineAgent.
In such case, we cannot rely on telemetry to get the decoding time.
Disable this test for now while we working on a fix.
Since this test is android only, just disable it

BUG=173184
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=180094

[qinmin, 2013-01-31 00:21:30]

PTAL

[tonyg, 2013-01-31 01:52:10]

Hey Nat, I want to get your thoughts on this patch. It looks like when impl side
painting got enabled, the image_decoding_benchmakr broke because the image
decoding events are no longer in the timeline. This patch reverts us back to
using the javascript measured metrics instead of the inspector metrics. That
will work for the synthetic pages, but eliminates the ability to run this
benchmark against real world pages. I'm not sure there's anything else we can do
for now, so I'm inclined to take this patch just to get the test green again.

[nduca, 2013-01-31 02:09:40]

I'd prefer we disable the test. The proper way to fix this is to use tracing for
this.

[tonyg, 2013-01-31 02:15:43]

On 2013/01/31 02:09:40, nduca wrote:
> I'd prefer we disable the test. The proper way to fix this is to use tracing
for
> this.

[+abarent, current perf sheriff]

Makes sense. To disable this test, we just need to add an early return statement
in MeasurePage, preferably for Android-only. We should do that asap while the
real fix to convert this test to parse out the events from tracing is being
worked on.

[qinmin, 2013-01-31 02:16:42]

I think this test is android only, not seeing it running on other perf bots.

On 2013/01/31 02:15:43, tonyg wrote:
> On 2013/01/31 02:09:40, nduca wrote:
> > I'd prefer we disable the test. The proper way to fix this is to use tracing
> for
> > this.
> 
> [+abarent, current perf sheriff]
> 
> Makes sense. To disable this test, we just need to add an early return
statement
> in MeasurePage, preferably for Android-only. We should do that asap while the
> real fix to convert this test to parse out the events from tracing is being
> worked on.

[qinmin, 2013-01-31 03:05:18]

Just changed the code to disable the test and its unit test.

On 2013/01/31 02:16:42, qinmin wrote:
> I think this test is android only, not seeing it running on other perf bots.
> 
> On 2013/01/31 02:15:43, tonyg wrote:
> > On 2013/01/31 02:09:40, nduca wrote:
> > > I'd prefer we disable the test. The proper way to fix this is to use
tracing
> > for
> > > this.
> > 
> > [+abarent, current perf sheriff]
> > 
> > Makes sense. To disable this test, we just need to add an early return
> statement
> > in MeasurePage, preferably for Android-only. We should do that asap while
the
> > real fix to convert this test to parse out the events from tracing is being
> > worked on.

[tonyg, 2013-01-31 23:20:07]

lgtm

https://codereview.chromium.org/12100007/diff/2002/tools/perf/perf_tools/imag...
File tools/perf/perf_tools/image_decoding_benchmark.py (right):

https://codereview.chromium.org/12100007/diff/2002/tools/perf/perf_tools/imag...
tools/perf/perf_tools/image_decoding_benchmark.py:10:
tab.StartTimelineRecording()
Should probably comment out this whole method too.

[qinmin, 2013-01-31 23:50:55]

https://codereview.chromium.org/12100007/diff/2002/tools/perf/perf_tools/imag...
File tools/perf/perf_tools/image_decoding_benchmark.py (right):

https://codereview.chromium.org/12100007/diff/2002/tools/perf/perf_tools/imag...
tools/perf/perf_tools/image_decoding_benchmark.py:10:
tab.StartTimelineRecording()
On 2013/01/31 23:20:07, tonyg wrote:
> Should probably comment out this whole method too.

Done.

[commit-bot: I haz the power, 2013-01-31 23:58:19]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/qinmin@chromium.org/12100007/10001

[commit-bot: I haz the power, 2013-02-01 05:58:55]

Change committed as 180094