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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx8jA-QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp8nHuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx8mt-wgM


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

chromium-rel-mac10
win-zenbook

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev   N   Good?
chromium@435132  0.809871  0.551252  25  good
chromium@435210  0.802858  0.682868  25  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 670726

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll_tbmv2
Test Metric: v8-gc-total_avg/v8-gc-total_avg
Relative Change: 0.87%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/618
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994370059844225920


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6452697274777600

| 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 Tests>AutoBisect.  Thank you!

Bisect failed to reproduce, regression appears to be within the noise level, and this appears to be a return to previous levels after a recent improvement.