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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/IMDB

Revision             Result                  N
chromium@496647      267.485 +- 474.657      21      good
chromium@496684      256.905 +- 492.2        21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=IMDB loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

Trying a pinpoint bisect on a wider range.

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/128e4429780000

Can't repro, on any platform. This is really weird, but there wer a lot of changes around this time, to the recording and the metrics.