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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_tW3pAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_syv-ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_t6VtQkM


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

chromium-rel-win7-gpu-intel

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

These are on master=ChromiumPerfFyi, so should be ignored despite the scary amount of regressions.

Pasted from the SpeedInfra chat:
Likely related to the catapult roll:
  https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/04dd47e541e2..30ce231266c6
Ned's changes in that roll changed the test

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : page_cycler_v2.intl_ja_zh
  Metric       : pcv1-cold-timeToFirstMeaningfulPaint_avg/http___www.google.com.hk__q_%E9%82%84%E6%8F%90%E4%BE%9B_fp_c44d333e710cb480


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.intl_ja_zh

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

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


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