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

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


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

android-one

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

===== 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@440628  89.2437  403.198  30  good
chromium@440659  101.467  450.245  30  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 677455

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2
Test Metric: v8-gc-incremental-step_max/v8-gc-incremental-step_max
Relative Change: 13.70%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1901
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8991947681539295504


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

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

this may be due to the changes to GC https://bugs.chromium.org/p/chromium/issues/detail?id=468240

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : ulan
  Commit : da328981ff11d136f484afc0638e919a8c781c62
  Date   : Thu Dec 22 16:14:09 2016
  Subject: [heap] Move GC tracer scope for incremental marking step one level up.

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : v8.infinite_scroll-ignition_tbmv2
  Metric       : v8-gc-incremental-step_max/v8-gc-incremental-step_max
  Change       : 908.62% | 4.24122222222 -> 42.7778

Revision                           Result                   N
chromium@440063                    4.24122 +- 0.725444      9      good
chromium@440361                    4.06297 +- 0.555902      6      good
chromium@440436                    4.23507 +- 0.338973      6      good
chromium@440473                    4.16057 +- 0.447449      6      good
chromium@440492                    4.21427 +- 0.516965      6      good
chromium@440494                    4.25633 +- 0.797592      6      good
chromium@440494,v8@0f12793f69      4.27003 +- 0.431303      6      good
chromium@440494,v8@da328981ff      33.9613 +- 62.767        6      bad       <--
chromium@440494,v8@f8f09ec50b      35.3241 +- 50.4405       6      bad
chromium@440495                    50.1894 +- 54.0531       6      bad
chromium@440497                    54.2815 +- 53.208        6      bad
chromium@440501                    52.1497 +- 64.9906       6      bad
chromium@440510                    34.8617 +- 43.9148       6      bad
chromium@440659                    42.7778 +- 75.8853       9      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2

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

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


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