Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999354108802277296

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2630
Failure reason: the build has failed.

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999352087674906976

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/749
Failure reason: the build has failed.

Bisect not working. But looks like this CL is the culprit:
https://codereview.chromium.org/2363343003

Reverting...

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

commit b524efc65e507803ec42e4d73509c420cb715081
Author: zhenw <zhenw@chromium.org>
Date: Sat Oct 08 17:33:08 2016

Revert of Add loading mobile story set (patchset #6 id:140001 of https://codereview.chromium.org/2363343003/ )

Reason for revert:
Failure on Android Perf bot

BUG= chromium:654215 

Original issue's description:
> Add loading mobile story set
>
> This adds a story set and corresponding benchmark for mobile loading
> performance loading team is interested in.
>
> Design doc: https://docs.google.com/document/d/1QKlZIoURAxZk-brrXsKYZl9O8ieqXht3ogeF9yLNFCI/edit
>
> BUG=643524
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
>
> Committed: https://crrev.com/31d0a108f1783a04f2b981d668883a43a30ddc32
> Cr-Commit-Position: refs/heads/master@{#423993}

TBR=kouhei@chromium.org,nednguyen@google.com,ksakamoto@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=643524

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

[modify] https://crrev.com/b524efc65e507803ec42e4d73509c420cb715081/tools/perf/OWNERS
[delete] https://crrev.com/ccd977fa5650bf395c59bbbb0afc81f5dbd3531c/tools/perf/benchmarks/loading.py
[modify] https://crrev.com/b524efc65e507803ec42e4d73509c420cb715081/tools/perf/benchmarks/page_cycler_v2.py
[delete] https://crrev.com/ccd977fa5650bf395c59bbbb0afc81f5dbd3531c/tools/perf/page_sets/data/loading_mobile.json
[delete] https://crrev.com/ccd977fa5650bf395c59bbbb0afc81f5dbd3531c/tools/perf/page_sets/data/loading_mobile_000.wpr.sha1
[delete] https://crrev.com/ccd977fa5650bf395c59bbbb0afc81f5dbd3531c/tools/perf/page_sets/data/loading_mobile_001.wpr.sha1
[delete] https://crrev.com/ccd977fa5650bf395c59bbbb0afc81f5dbd3531c/tools/perf/page_sets/loading_mobile.py

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

commit eff0660d223203c7e081c9fbdb7ad0e4cf425d15
Author: ksakamoto <ksakamoto@chromium.org>
Date: Thu Oct 13 03:47:34 2016

Enable loading.mobile benchmark on Android except reference and webview

Note to sheriffs: If there are failures/crashes on waterfall bots,
please comment out individual pages in tools/perf/page_sets/loading_mobile.py
instead of disabling the whole benchmark.

BUG=643524, 654215 
CQ_INCLUDE_TRYBOTS=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/2409103002
Cr-Commit-Position: refs/heads/master@{#424949}

[modify] https://crrev.com/eff0660d223203c7e081c9fbdb7ad0e4cf425d15/tools/perf/benchmarks/loading.py

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982651789605443392

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982611816003558176

=== Auto-CCing suspected CL author ksakamoto@chromium.org ===

Hi ksakamoto@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Test failure found with culprit

Suspected Commit
  Author : ksakamoto
  Commit : 31d0a108f1783a04f2b981d668883a43a30ddc32
  Date   : Fri Oct 07 22:52:31 2016
  Subject: Add loading mobile story set

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstContentfulPaint_avg/https___www.google.com_search?q_flower_q_flower+delivery

Revision             Exit Code      N
chromium@423987      1 +- N/A       5      good
chromium@423991      1 +- N/A       5      good
chromium@423992      1 +- N/A       5      good
chromium@423993      0 +- N/A       5      bad       <--
chromium@423995      0 +- N/A       5      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests loading.mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982651789605443392

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5214982285819904


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!