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

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


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

linux-release

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@413413  40.0874  0.96765  5  good

Bisect job ran on: linux_perf_bisect
Bug ID: 659510

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.intl_ja_zh
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-cold/http___www.google.com.hk__q_%E9%82%84%E6%8F%90%E4%BE%9B_fp_c44d333e710cb480
Relative Change: None
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6794
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997755337604188272


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

| 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!

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2710
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@413413  105.149  1200.13  21  good
chromium@424862  N/A      N/A      0   bad

Bisect job ran on: linux_perf_bisect
Bug ID: 659510

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.google.com.hk..q..E9.82.84.E6.8F.90.E4.BE.9B.fp.c44d333e710cb480 page_cycler_v2.intl_ja_zh
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-cold/http___www.google.com.hk__q_%E9%82%84%E6%8F%90%E4%BE%9B_fp_c44d333e710cb480
Relative Change: 100.00%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6946
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993072610386948688


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

| 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!

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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.