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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : percentage_smooth/http___techcrunch.com

Revision             Result                  N
chromium@446169      75.3766 +- 71.8598      21      good
chromium@446229      71.2061 +- 68.4286      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=http...techcrunch.com smoothness.top_25_smooth

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

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


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

The ref doesn't seem to be working for this metric :(

From the shape of the graph it looks like something landed and got reverted.  I think we can ignore.