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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg56D-rAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg54TrpAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg59DovAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx7nphwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp470vgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp52vkQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5_y-pAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5835sQoM


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

android-nexus6
android-nexus7v2
android-nexus9

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

===== 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@435425  1708937  433480   27  good
chromium@435479  1712588  428923   27  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 672523

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.hackernews v8.browsing_mobile_ignition
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:code_and_metadata_size_avg/browse_news/browse_news_hackernews
Relative Change: 0.21%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2811
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993826453405289792


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

| 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/8992648268682620272

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2847
Failure reason: the build has failed.
Additional errors:
Bisect aborted early for lack of confidence.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

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

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

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : v8.browsing_mobile_ignition
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:code_and_metadata_size_avg/browse_news/browse_news_qq

Revision             Result                 N
chromium@435378      1515528 +- 131280      21      good
chromium@435479      1529173 +- 159654      21      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 --story-filter=browse.news.qq v8.browsing_mobile_ignition

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

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


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

Not actionable.