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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglNna-AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglK-hugsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1JaBvAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1NinqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg1IHx7AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglJKuvQkM


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

chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac12
chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : V8 C++:duration_avg/browse_media/browse_media_tumblr

Revision             Result                  N
chromium@453923      222.577 +- 22.3066      21      good
chromium@453979      221.891 +- 17.7471      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=browse.media.tumblr v8.runtimestats.browsing_desktop

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

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


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

It seems, this one can be closed.