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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=2bcf865db60cfc6c48880e8187689fe0cdba8d419509d4d42e7280e0b5d11f2f


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

chromium-rel-mac-retina

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-cold/HTML5Rocks

Revision             Result                  N
chromium@494277      53.3124 +- 11.8568      14      good
chromium@494830      128.737 +- 35.5373      14      bad

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=HTML5Rocks loading.desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970275661767639056


For feedback, file a bug with component Speed>Bisection

Regression range unclear; re-bisecting with pinpoint.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/148e4429780000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/148e4429780000

Enable Finch Trial Test for MacV2Sandbox.
By kerrnel@chromium.org · Tue Aug 15 19:42:42 2017
chromium @ 9705b7aaabf4c81d4e9cb13174338df9bde61cc4

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Bisect unable to find culprit. This exists in stable. Ignoring.