=== Auto-CCing suspected CL author nyquist@chromium.org ===
Hi nyquist@chromium.org, the bisect results pointed to your CL, please take a look at the
results.
=== BISECT JOB RESULTS ===
Perf regression found with culprit
Suspected Commit
Author : nyquist
Commit : 0e1252cce0bae1c59bfd1c1c998f8206258b3123
Date : Wed Feb 08 23:09:26 2017
Subject: Revert of [Omaha] Make the whole pipeline run each time (patchset #4 id:60001 of https://codereview.chromium.org/2665133005/ )
Bisect Details
Configuration: android_nexus6_perf_bisect
Benchmark : memory.top_10_mobile
Metric : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
Revision Result N
chromium@449079 0.0 +- 0.0 6 good
chromium@449109 0.0 +- 0.0 6 good
chromium@449124 0.0 +- 0.0 7 good
chromium@449126 0.0 +- 0.0 5 good
chromium@449127 182764 +- 0.0 6 bad <--
chromium@449128 182764 +- 0.0 6 bad
chromium@449131 182764 +- 0.0 6 bad
chromium@449138 182764 +- 0.0 6 bad
chromium@449196 182764 +- 0.0 6 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 memory.top_10_mobile
Debug Info
https://chromeperf.appspot.com/buildbucket_job_status/8988099202578537008
Is this bisect wrong?
https://chromeperf.appspot.com/bad_bisect?try_job_id=5860741162205184
| 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!
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 9 2017