All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=675703

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgz_Dz6QoM


Bot(s) for this bug's original alert(s):

android-nexus5

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

=== PERF REGRESSION ===


=== 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 =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : [FirstMeaningfulPaint] Do not stop observing layouts before FirstContentfulPaint
Author  : ksakamoto
Commit description:
  
This should mitigate a bug that FirstMeaningfulPaint is reported too
soon (or not reported) on some CPU-heavy pages, because network idle is
detected while CPU is busy running scripts.

BUG= 659021 , 674228 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

Review-Url: https://codereview.chromium.org/2581633002
Cr-Commit-Position: refs/heads/master@{#438791}
Commit  : 2b891d60b92a6066fa1620794e244ef6e0ce65e2
Date    : Thu Dec 15 09:27:55 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@438776  1195.35  1115.61  14  good
chromium@438788  1192.33  738.133  9   good
chromium@438790  1184.71  120.35   6   good
chromium@438791  1816.71  200.121  6   bad    <--
chromium@438794  1793.08  249.43   9   bad
chromium@438799  1842.82  221.507  9   bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 675703

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.drive system_health.common_mobile
Test Metric: timeToFirstMeaningfulPaint_avg/load_tools/load_tools_drive
Relative Change: 54.17%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4474
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8992815503340260864


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5793226739417088

| 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 Tests>AutoBisect.  Thank you!

This is working as intended. Before my change, first meaningful paint was reported incorrectly.