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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@407631  5802088  745240   2  good
chromium@407786  7219774  1106847  5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 633983

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.browsing_mobile
Test Metric: browse_social-memory:chrome:renderer_processes:reported_by_chrome:v8:allocated_by_malloc:peak_size_max/browse_social_facebook
Relative Change: 14.07%
Score: 0

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


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

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

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@407631  5187371  1049854  12  good
chromium@407740  5626458  808280   18  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 633983

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.browsing_mobile
Test Metric: browse_social-memory:chrome:renderer_processes:reported_by_chrome:v8:allocated_by_malloc:peak_size_max/browse_social_facebook
Relative Change: 11.99%
Score: 0

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


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

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