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

===== 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@424076  8073917  754789   27  good
chromium@424078  8031589  884622   27  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 672278

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.m.youtube.com.results.q.science memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_m_youtube_com_results_q_science
Relative Change: 0.52%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4421
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993891597656199808


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

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

So now we can't repro with bisect bots. Did I do something wrong?

Same with this.

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

Uhm the bisect doesn't seem to repro. The jump on the dashboard is +550 K roughly but the output in #2 says 40k. Kicked another bisect, but I think you are doing everything right.

===== 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@424076  8057064  940294   27  good
chromium@424078  8100129  829669   27  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 672278

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.m.youtube.com.results.q.science memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_m_youtube_com_results_q_science
Relative Change: 0.53%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4426
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993842759383603376


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

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

40k jump again. 

Adding Simon in case he has ideas.

https://bugs.chromium.org/p/chromium/issues/detail?id=672183

Had memory.top_10_mobile and system_health.memory_mobile both not reproducing via bisect until you got rid of --story-filter. I'll re-kick this.

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

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


=== Bisection aborted ===
The bisect was aborted because Infra Failure: Step('Working on revision chromium@424075,v8@55af3c44c9.install ChromePublic.apk') returned 2
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@424075  7613934  49277.6  8  good
chromium@424076  8186502  13381.8  5  bad
chromium@424077  8153017  138693   5  bad
chromium@424078  8136147  145287   5  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 672278

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_chrome:v8:effective_size_avg/foreground/http_m_youtube_com_results_q_science
Relative Change: 6.86%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4429
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993804660038856320


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

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

Well, this is what we expected, it's the V8 roll. But we need to bisect all of these: https://chromium.googlesource.com/v8/v8/+log/73a37f6c..e717dafa

How does that work if you remove --story-filter?

That failure message looks like https://bugs.chromium.org/p/chromium/issues/detail?id=672529, where the builders have been producing invalid builds. The bisect won't be able to progress further until that's fixed unfortunately.

re: #c12

Sorry, I missed your comment. Although root causes isn't known yet, running with --story-filter stops any of the other stories from running. They're supposed to be independent and thus, shouldn't matter if one or all of them run, but that's not the case right now.

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@424075  7611066  62032.5  6  good
chromium@424076  8162609  145972   6  bad
chromium@424077  8130519  187458   6  bad
chromium@424078  8185019  18369.0  6  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 672278

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_chrome:v8:effective_size_avg/foreground/http_m_youtube_com_results_q_science
Relative Change: 7.54%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4472
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8992844203467519664


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

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

Is this related to crbug.com/664880?

No this is  crbug.com/675712 , basically older revisions fail to build now.

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_m_youtube_com_results_q_science

Revision             Result                 N
chromium@424076      8073917 +- 754789      27      good
chromium@424078      8031589 +- 884622      27      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.m.youtube.com.results.q.science memory.top_10_mobile

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

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


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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.