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

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


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

android-nexus6

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

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

+perezju for FYI. Noogler sheriff here, but I didn't see an obvious culprit. The metric seemed to regress slightly and become *more* stable, which seems odd. Was there a benchmark change by any chance? We'll see what the bisect says?

===== 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@424412  173841522  252602   18  good
chromium@424486  173763015  381334   18  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 657057

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=http.www.amazon.com.gp.aw.s.k.nexus memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus
Relative Change: 0.00%
Score: 0

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


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

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

===== 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@424412  162668544  5624070  18  good
chromium@424436  165601508  6968251  18  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 657057

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus
Relative Change: 1.76%
Score: 0

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


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

| 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 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@424400  173900459  258360   18  good
chromium@424486  173772800  329985   18  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 657057

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=http.www.amazon.com.gp.aw.s.k.nexus memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus
Relative Change: 0.09%
Score: 0

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


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

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

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64ati_perf_bisect/builds/1620
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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


===== TESTED REVISIONS =====
Revision         Mean       Std Dev  N    Good?
chromium@424412  173862093  316053   210  good

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 657057

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=http.www.amazon.com.gp.aw.s.k.nexus memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus
Relative Change: 0.33%
Score: 0

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


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

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/863
Failure reason: the build has failed.
Additional errors:
Either of the initial "good" or "bad" revisions failed to be tested or built.

+dtu, this one has been having troubles to bisect

The output is so hard to read! Looks like there is a build failure, but I can't see on what revision:
https://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/863/steps/Gathering%20reference%20values.buildbucket.get%20%282%29/logs/json.output

https://build.chromium.org/p/tryserver.chromium.perf/builders/mac_perf_bisect_builder/builds/9141/steps/generate_build_files/logs/stdio

Bisect is really brittle to this. I know pinpoint would make it easier to understand which revisions we can't build, and at some point get the option to patch in reverts, but in the short term is there an easy way to figure out which revisions don't build and bisect around them?

This was collecting three apparently very different regressions.

- one in gpu in memory.top_10_mobile, has recovered since.
- one in scroll update latency smoothness.top_25_smooth, the regression was returning to the mean after an earlier change.
- one in v8.infinite_scroll-ignition_tbmv2, hasn't recovered.

I'm going to won't fix this bug for the first two, and split off the 3rd to  issue 675591 .

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

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus

Revision             Result                    N
chromium@424412      173901922 +- 1016049      21      good
chromium@424436      173927473 +- 1174087      21      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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=http.www.amazon.com.gp.aw.s.k.nexus memory.top_10_mobile

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

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


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