Issue metadata
Sign in to add a comment
|
1.1%-1.6% regression in memory.top_10_mobile at 441282:441306 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8991276005457157696
,
Jan 5 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_one_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/foreground/http_www_baidu_com_s_word_google Revision Result N chromium@441281 15238675 +- 434052 21 good chromium@441306 15250462 +- 468158 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=http.www.baidu.com.s.word.google memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8991276005457157696 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6386613012135936 | 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!
,
Jan 6 2017
These alerts overlap with bug 678580 , will dupe into that. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sullivan@chromium.org
, Jan 5 2017