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

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


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

chromium-rel-mac-retina

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/TheVerge

Revision             Result                  N
chromium@494990      507.974 +- 181.524      21      good
chromium@495262      470.314 +- 235.687      21      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=TheVerge loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12c22180780000

These graphs have a weird ramp up instead of a sharp regression. Trying a pinpoint bisect on a wider range.

📍 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/12c22180780000

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

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