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

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


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

chromium-rel-mac-retina
chromium-rel-mac11

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@427824  134.139  1.66063  8   good
chromium@427835  134.117  2.57727  18  good
chromium@427840  135.504  1.8275   18  bad
chromium@427845  206.334  53.7333  12  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 660550

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: timeToFirstContentfulPaint_avg/pcv1-cold/http___www.baidu.com_s?wd_%D0%C2%20%CE%C5
Relative Change: 63.71%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1774
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997521088866454224


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

| 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/8997428692553415584

Re-running biscet. >:-|

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1775
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.

Cannot bisect. I get a different "infra failure" reason each time.

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

Kicking off a bisect on the Mac 11 bot, which has a smaller revision range and also to check if it's less error prone than the retina.

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/984
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.

Dave, can you take a look as part of your bug triage rotation?

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : page_cycler_v2.intl_ja_zh
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___www.baidu.com_s?wd_%D0%C2%20%CE%C5


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter='http...www\.baidu\.com.s\?wd.\%D0\%C2\%20\%CE\%C5' page_cycler_v2.intl_ja_zh

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

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


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

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